We have two roles available on IT Shop:

- Business Role A 

- Business Role B

How to create an SOD which prevents user to submit request if the user is not member of both A & B roles ?

Imagine a scenario where you have AD controlling access to hundreds (this is the key word here) of applications meaning that a single AD group actually represents an entitlement in a specific application.

Let's say that my current rules are  doing checks…

Currently we have more than 180 SoD Rules defined, which should be checked directly during the save process in the Web Shop to give the user direct feedback if the request could be send or not.

In version 6 the overall performance for an end user as acceptable…

Hey Folks,

We are testing a scenario where we have nested business role hierarchies that inherit entitlements at various levels. This seems to be working ok, but I have been asked to develop a use case where a person can request a role via the ITShop that…

SAP-GRC integration: Best Practices to use SAP-GRC for SoD analysis (Risk assessment)

Hello Experts,

Quick: I am wondering how to integrate SAP-GRC for SoD analysis in the best way.

For sure, Identity Managers in-built risk module could be use in order…