Click HERE to see how Saviynt Intelligence is transforming the industry. |
08/29/2024 01:31 AM
Hi Team -
For preventative SOD check, we have below 2 rulesets
1) ZALL - Evaluate SODs in Access Request as 'Yes'
2) BIOBRK-Finance-SOD-SetOne - Evaluate SODs in Access Request as 'Yes'
ZALL is for SAP with type SAP and BIOBRK-Finance-SOD-SetOne is for a different endpoint with type Non-SAP.
The issue is while requesting access to SAP for a user, we are seeing the SOD violations flagged from under BIOBRK-Finance-SOD-SetOne which is not having any functions or entitlements part of SAP. Why does this happen? Can we avoid this from happening?
Thank you
08/29/2024 01:34 AM
Hi @shivmano in the function of BIObsk did you any conflicting entitlement?
Can you share ruleset and function details
08/29/2024 05:41 PM
08/30/2024 01:53 AM - last edited on 08/30/2024 02:36 AM by Sunil
@NM @rushikeshvartak - Here is the screenshot the BIOBRK-Finance-SOD-SetOne violation showing on the request page for SAP endpoint. Also none of the entitlements in the BIOBRK-Finance-SOD-SetOne functions are from SAP endpoint.
Ruleset (BIOBRK-Finance-SOD-SetOne)
Ruleset (SAP) - ZALL
[This message has been edited by moderator to disable url hyperlink]
08/30/2024 02:16 AM
@shivmano what is the function type for (BIOBRK-Finance-SOD-SetOne) function
08/30/2024 03:08 AM
@NM it is Non-SAP
08/30/2024 08:08 AM
This is expected behavior; please refer https://forums.saviynt.com/t5/identity-governance/sod-owner-approval-generated-in-case-of-no-violati...
existing SOD will be visible
below is configuration to disable [Global config - SOD ]