Oracle Access Manager (OAM)11g - Custom Plugin Fails to Set Correct User Identity Store After Restart of OAM
Last updated on JANUARY 24, 2017
Applies to:Oracle Access Manager - Version 220.127.116.11.1 and later
Information in this document applies to any platform.
After restarting Oracle Access Manager (OAM) server, a custom authentication plugin which queries the user for the identity store to authenticate with fails. Instead of using the user identity store selected by the user, the default user store (in this case UserIdentityStore1) is used for the authentication, which causes the authentication to fail.
The issue could be worked around by either clicking the "Apply" button in the OAM Administration Console for any of the defined user stores, or by authenticating successfully using an out of the box authentication scheme after OAM was started. Once the workaround is applied, the custom authentication plugin works as desired until OAM is restarted.
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