Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

All entitlement approvals going to SOD owner approval

sakshibansal
New Contributor II
New Contributor II

Hi,

All the entitlements in a request are going to sod owner approval even if they are not part of SOD. I understand this is the expected behavior.

Is there any other option/config we can do to avoid this in a Parallel or Serial workflow? So that the non sod entitlements approval doesn't go to SOD owners?

9 REPLIES 9

Amit_Malik
Valued Contributor II
Valued Contributor II

Hi @sakshibansal , that is not expected behavior. Most probably it would be the way workflow is written , Can you share the workflow or screenshots of it.

You would need to use If else condition like SODViolation.get('Medium') > 0 and if no violation --> go normal path else SOD Path.

 

Thanks,

Amit

If this answers your query, Please ACCEPT SOLUTION and give KUDOS.

Kind Regards,
Amit Malik
If this helped you move forward, please click on the "Kudos" button.
If this answers your query, please select "Accept As Solution".

rushikeshvartak
All-Star
All-Star

This is known defect and getting fixed in 24.7 

 SOD-2855

Refer https://forums.saviynt.com/t5/identity-governance/sod-approval-workflow-issue/m-p/97338#M63749


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

adarshk
Saviynt Employee
Saviynt Employee

Team,

Per the latest update, this fix would be available by 24.8 

Thanks,

Manu269
All-Star
All-Star

@sakshibansal 

Entire Request with all the entitlements will be going to the Risk owners.

It is an expected behavior as per the current product behavior with the SOD owner block.

Lets hope this get ammended as per input from @adarshk 

Regards
Manish Kumar
If the response answered your query, please Accept As Solution and Kudos
.

Its not expected behaviour, Its defect this functionality was working in Non-EIC


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

sakshibansal
New Contributor II
New Contributor II

@rushikeshvartak We were getting this issue in v5.5 as well. In some of the old forums post, you mentioned that it is an expected behavior.

For reference, https://forums.saviynt.com/t5/identity-governance/sod-approver-is-getting-all-entitlements-even-thou...

If you want to route based on sod priority then it should go to respective owner it was working before. In previous post i stated if there is sod then full request will go for group approval as it was discussion on user group as approval and not risk owner


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

We have the similar approval workflow in v5.5 where we check SOD > 0. But instead of group owner, we have configured SOD Owner approval block, So all entitlements in a request including the ones without SOD went to SOD owner for approval. Is this an expected behavior in Non EIC version?

If not, then it was not working in 5.5, so probably a bug there as well.

Its expected so owner can validate all ents requested


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.