Skip to Content
author's profile photo Former Member
Former Member

How to avoid conflicts for the roles which are not in use in RAR

Hi all,

We are not using some roles and no users have been assigned to these roles. But when we are running Role level SOD analysis RAR is throwing conflicts even for these roles.

Is there a way where we can avoid these roles for consideration like that of Ignore Locked and Expired users in User analysis?

Thanks and Best Regards,

Srihari.K

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Nov 10, 2009 at 06:50 AM

    Hi Sri,

    Yes, you can exclude object from an analisys when you schedule a background job. Roles, profiles, users or user goups are objects that can be excluded. But the question why you want to exclude a role? If it's not in use, investigate if you can delete it.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 10, 2009 at 06:57 AM

    Hi,

    When you do not use that roles ,Please delete in back end again do the full sync back ground job in GRC , now the old roles wont be there in GRC, only the roles which exists in back end will be there , do the role level analysis now .

    Otherwise if you have fallowed proper naming convention , don't include that unnecessary roles for analysis, while selecting that roles in analysis E.G ZZECC.*

    Regards,

    Joseph

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      I suspect that you will need to re-sync the roles with RAR to update the fact that they have been amended.

      Check the status of the background jobs to check when this was last done.

      Otherwise, you can just restrict them from each report you run but you will then need to remember to do this every time.

      It is better to try to tackle the root cause rather than just work around it wherever possible.

      Simon

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.