Last updated on MARCH 08, 2017
Applies to:Oracle Containers for J2EE - Version 10.1.2.3.0 and later
Information in this document applies to any platform.
***Checked for relevance on 16-Sep-2013***
Custom Java application is deployed on OC4J and configured as partner application to SSO.
- Unable to login to the application with newly created users and errors out with "HTTP 403 Forbidden Error".
- Existing users are able to login.
- The new users are able to login to OIDDAS and also ldapbind against OID works fine.
After initial investigation, it was found that the newly created user was not part of the Group authorized by the application (Specified through the security settings in orion-application.xml and web.xml of the application). Even after the newly created user was assigned the role/group required by the application, the HTTP 403 error persisted. With no further changes made, the same user worked fine after a few hours.
Why is this delay and how can this be avoided?
Oracle Application Server 10.1.2.3.0
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms