How To Refresh The OAM 11g User / Group Membership Cache?
(Doc ID 1339686.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Access Manager - Version: 22.214.171.124.0 to 126.96.36.199.0
Information in this document applies to any platform.
A user is accessing Resource1 which is protected by OAM 11g Release 1 (11.1.1.x). The user can view the protected page after OAM SSO login because the user is member of Group1: the OAM Authorization Policy for Resource1 allows access to members of that group.
The user cannot access Resource2 because the OAM Authorization Policy for Resource2 only allows access to Group2 members. The user is not a member of Group2.
At this point if a change is made in the LDAP Server which is the OAM User Data Store to add the user as a member of Group2:
- Would the user immediately be able to access Resource2?
- If not, how to force OAM 11g to refresh the user's cached group membership information?
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.|