Refreshing user roles in 12c — Oracle Analytics

Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Refreshing user roles in 12c

Received Response
22
Views
3
Comments
Mark.Thompson
Mark.Thompson Rank 6 - Analytics Lead

Quite frequently, if I add, delete, or change a group in WLS, then assign that group to a role in Fusion Middleware, any users who are assigned to that WLS group do not immediately see the results.  For example, I created a WLS group called OW_ANALYST.  I assigned a user to that group.  I assigned that group as a member of the BIContentAuthor role.  I signed in as the user in question, but did not see any options under 'New' to create new analyses, dashboard prompts, and so forth.  But after a few minutes, I signed in again, and those options suddenly appeared. 

It appears that there is some security refresh mechanism going on behind the scenes, and that the refresh doesn't happen immediately - there is a several minute lag involved.  It feels as if WLS Groups and FMC Roles aren't "in sync" for some period of time, until that refresh cycle hits.

Is there any function that allows us to manually sync the Groups in WLS and the Roles in FMC on request, rather than waiting for the background sync to occur?  Or is it something else that causes the user privileges to have a delayed reaction to the changes in WLS and FMC?

Answers

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    I think we discussed this already a while back but can't remember whether it was in here or in our chat channel.

    The latency you mention is rather tied to OPSS than WLS itself and I'm not aware that you can fiddle with that. OPSS does cache its data...prime example 2412508.1 or 1588912.1

  • Mark.Thompson
    Mark.Thompson Rank 6 - Analytics Lead

    Thanks, Christian.  I navigated to 1588912.1 and found this note (see below) at the bottom, along with the suggested workaround, which is basically to restart the entire WLS domain.  Since that is not really a great option for us, I'll live with the delay.  THANK YOU for the reply.

    Note: Due to the OPSS policies caching at WebLogic Domain layer, it might take some time for the policies modification to be effective. If you want to avoid this delay, stop and restart the complete WebLogic Domain

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    Yeah I didn't want to suggest restarting it all - alas that's what it seems to come down to.