HTTP-500 Internal Server Error With 3rd Party Integrated SSO Login
(Doc ID 403207.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Application Server Single Sign-On - Version 9.0.4 to 10.1.4 [Release 10gR1 to 10gR3]
Information in this document applies to any platform.
***Checked for relevance on 21-FEB-2013***
SSO has been integrated with a 3rd party access management system following the SSO documentation 'Integrating with Third-Party Access Management Systems'.
When the application page protected by the third party access management system is loaded, the user is redirected to the third party access management system login interface and enters valid credentials there.
Control is then passed back to the application page which is protected by 10gAS OSSO. Since an SSO session does not yet exist, the user is redirected behind the scenes to SSO to complete SSO login. SSO does not perform authentication, since this is delegated to the 3rd party access management system using a custom plugin. SSO only retrieves the user data for the userid passed from the access management system and creates the SSO_ID session cookie.
However SSO is failing to establish the SSO session; when the user is redirected to SSO the HTTP-500 error occurs:
500 Internal Server Error
Unexpected Error. Please contact Administrator
The debug ssoServer.log shows error:
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
|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.|