My Oracle Support Banner

OAM 10g: After OAM/SSO Integration Login Produces an HTTP-500 Internal Server Error - No site2pstoretoken from SSO partner Application (Doc ID 602260.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Application Server Single Sign-On - Version: 10.1.4.0.1 and later   [Release: 10gR3 and later ]
COREid Access - Version: 10.1.4.0.1 and later    [Release: 10g and later]
Information in this document applies to any platform.
Oracle Single Sign-On - Version: 10.1.4.0.1
Checked for relevance on 11-Apr-2010

Symptoms

Unable to Login to SSO or OIDDAS after configuring Single SignOn (10.1.4.0.1) with  Oracle Access Manager 10g (10.1.4.0.1) ,

Browser shows HTTP-500 Internal Server Error

ssoServer.log shows the following error:

Tue Jun 10 06:02:00 GMT 2008 [ERROR] AJPRequestHandler-ApplicationServerThread-5 No site2pstoretoken from SSO partner
Tue Jun 10 06:02:00 GMT 2008 [ERROR] AJPRequestHandler-ApplicationServerThread-5 Unexpected Exception received
java.lang.NullPointerException
at oracle.security.sso.server.policy.FilePolicyManager.getAuthLevel(FilePolicyManager.java:396)
at oracle.security.sso.server.auth.AuthDirector.getAuthLevel(AuthDirector.java:234)
at oracle.security.sso.server.ui.SSOLoginServlet.doPost(SSOLoginServlet.java:480)
at oracle.security.sso.server.ui.SSOLoginServlet.doGet(SSOLoginServlet.java:333)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:826)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:332)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)

Changes

Confgured SSO with Oracle Access Manager.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
  Symptoms
  Changes
  Cause
  Solution
     Verify that the policy domain is properly spelled:
     Verify that the correct HTTP Header is Returned
     

The XXX_HEADER_VAR should be the same as given in SSOOblixAuth.java for the OBLIX_USER_NAME string.

.....................................

public class SSOOblixAuth implements IPASAuthInterface { private static String OBLIX_USER_HEADER = "XXX_HEADER_VAR"; private static String CLASS_NAME = "SSOOblixAuth"; .........................................



This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.