SAP Knowledge Base Article - Preview

3234929 - Failing flow in FPN after engine JNDI security fix (NW 7.50 SP 25)

Symptom

  • After upgrading the system to NW 7.50 SP25 or higher, Enterprise Portal Federated Portal Network (FPN) stopped working
  • FPN Remote Delta Link (RDL) scenarios stopped working
  • When pasting remote content as local content via the Portal Content Management, the paste operation fails with the following error: “Could not create remote delta link to object '<PCD path>. Could not connect to the remote portal. The remote portal may be down, there may be a network problem, or your connection settings to the remote portal may be configured incorrectly”.
  • When changing Remote Delta Link object on the consumer side, the changes fail to be synchronized on the producer side (where the content is eventually rendered). As a result, a “Portal runtime exception” happens:
     
    The following stack trace can be found in Producer side:

    FPN failed to lookup for remote object 'pcd:portal_content/…………' 
    [EXCEPTION]
    com.sap.portal.fpn.exception.unchecked.RemoteInfrastructureFailureException: Could not get to the remote side
    at com.sap.portal.fpn.remote.accessor.FPNRemoteAccessor.getRemoteInitialContext(FPNRemoteAccessor.java:244)
    at com.sap.portal.fpn.remote.accessor.FPNRemoteAccessor.init(FPNRemoteAccessor.java:125)

    ………

    Caused by: javax.naming.NamingException: Exception while trying to get InitialContext. [Root exception is java.lang.SecurityException: User 'Guest' is not authorized.]
    at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:386)
    at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:64)
    at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:45)
    at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
    at javax.naming.InitialContext.init(InitialContext.java:244)
    at javax.naming.InitialContext.<init>(InitialContext.java:216)
    at com.sap.portal.fpn.remote.accessor.FPNRemoteAccessor.getRemoteInitialContext(FPNRemoteAccessor.java:199)
    ... 65 more
    Caused by: java.lang.SecurityException: User 'Guest' is not authorized.
    at com.sap.engine.interfaces.security.SecurityThreadContext.checkAuthorized(SecurityThreadContext.java:150)
    at com.sap.engine.interfaces.security.SecurityThreadContext.checkAuthorized(SecurityThreadContext.java:132)




Read more...

Environment

  • NetWeaver Application Server Java
  • Enterprise Portal 

Product

SAP Enterprise Portal all versions ; SAP NetWeaver 7.5 ; SAP NetWeaver Application Server for Java all versions

Keywords

FPN upgrade stopped working not working broke update patch federated portal network producer consumer , KBA , EP-PIN-FPN , Federated Portal Network , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.