Symantec Access Management

  • Private Community

  • 1.  The federation partnership is failing with java null pointer exception

    Posted Oct 15, 2018 03:37 PM

    Hello

     

    Policy Server,Platform=Windows version 6.2  (Build 9200),Version=12.52,Update=02.01,
    Proxy Sever = Linux 2.6.32-754.2.1.el6.x86_64
    CA SiteMinder Option Pack for Web Agent - 12.52.0.142
    Webagent Version - 12.52.0.142  Build Number=142 Update=0
    Server version: Apache/2.2.15 (Unix)
    FWS installed on tomcat - apache-tomcat-7.0.28

     

     

     

     

    We are getting the below error in the trace logs for an IDP Initiated federation. What could this mean?

     

    [10/15/2018][18:51:30][10129][1983399680][2339a05f-ecb1e728-acd264c2-1ec2537f-127ee251-3a4][AssertionConsumer.java][doPost][Exception caught in class com.netegrity.affiliatemind
    er.webservices.saml2.AssertionConsumer, method doPost, message java.lang.NullPointerException.]
    [10/15/2018][18:51:30][10129][1983399680][2339a05f-ecb1e728-acd264c2-1ec2537f-127ee251-3a4][AssertionConsumer.java][doPost][Stack Trace: java.lang.NullPointerException
            at com.netegrity.affiliateminder.webservices.saml2.dk.a(DashoA10*..:231)
            at com.netegrity.affiliateminder.webservices.saml2.dk.b(DashoA10*..:181)
            at com.netegrity.affiliateminder.webservices.saml2.AssertionConsumer.a(DashoA10*..:1484)
            at com.netegrity.affiliateminder.webservices.saml2.AssertionConsumer.doPost(DashoA10*..:656)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
            at com.netegrity.affiliateminder.webservices.CAFedFilter.doFilter(DashoA10*..:58)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
            at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
            at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
            at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
            at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
            at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
            at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
            at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
            at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
            at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:200)
            at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
            at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
            at java.lang.Thread.run(Thread.java:745)
    ]
    [10/15/2018][18:51:30][10129][1983399680][2339a05f-ecb1e728-acd264c2-1ec2537f-127ee251-3a4][AssertionConsumer.java][doPost][Ending SAML2 AssertionConsumer Service request proces
    sing with HTTP error 500]

     

     

     

    CA Technologies occasionally uses files that were provided by customers as part of their support engagement for troubleshooting their support issues and for testing future releases of our products to help ensure that the fixes for each customer remain fixed in such releases. CA Technologies continues to maintain the same degree of care and confidentiality as it does with all received customer information. Please select No if you do NOT permit the use of the file on this case for CA Technologies testing.


  • 2.  Re: The federation partnership is failing with java null pointer exception

    Broadcom Employee
    Posted Oct 16, 2018 05:24 PM

    Hi, 

    I would suggest going ahead and creating a Support ticket. The reason I am suggesting this is that under a normal error reporting scenario, we should not be getting a Null Pointer Exception, we should be returning a proper error message. By opening the Support ticket, not only can we help you resolve the issue, but we can get the error handling updated so that in the future the Null Pointer Error is not returned.

     

    Based on what you have provided, I don't see enough information to know what specifically is the root cause. We might need to get the error handling corrected first or get an instrumented build deployed in order to see what is happening in the flow.

     

    Thanks!



  • 3.  Re: The federation partnership is failing with java null pointer exception
    Best Answer

    Broadcom Employee
    Posted Oct 18, 2018 04:06 PM

    Hello Rucha,

     

    There could be a number of different reasons for a Null Pointer Exception.

     

    First of all, you will need to upgrade to latest patch of agent option pack, considering the policy server is already on SP2 CR1 and agent option pack has no patch applied.

    Once that is done, then test use case again and check what else could be wrong.

     

    Thank you,

     

    Hongxu Liu