My Oracle Support Banner

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: to
Information in this document applies to any platform.


How to refresh a user's cached group membership information after Oracle Access Manager (OAM) Single Sign-On (SSO) login?

Example scenario:

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:


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.

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