Leveraging Intelligent Recommendations for Operational Transformation. AMS Partners click HERE | EMEA/APJ Partners click HERE |
07/10/2024 12:35 AM
Hi All,
In one of our implementations, we are using Saviynt app for ServiceNow (SNOW) plugin and customer wants SNOW to be used as access request form for end users, Saviynt will only be used to complete provision and deprovision tasks following with fulfilling the access in target applications.
For one of the AD based logical applications, SoD is implemented for 3 entitlements (ent_1, ent_2, ent_3) no user can have any 2 ents together in their accounts for that application/endpoint.
While raising request through ARS in saviynt, the preventative SoD is working fine and its showing violation to requester.
But when raising same access with 2 ents (Eg., ent_1, ent_2) in SNOW request form after request submission, the SoDviolation is not showing anywhere.
Am i missing any configuration here? We have enabled SoD in ruleset, global config and SavRole level
07/10/2024 06:34 AM
Is it visible in saviynt ?
07/10/2024 06:39 AM
Yes the SoD violations are showing in Saviynt ARS request after I select the same user with same entitlements request.
But when exact same request is getting raised via ServiceNow then it is not highlighting SoD
07/10/2024 06:41 AM
Check checksod - true/false, flag in service now api call
https://documenter.getpostman.com/view/36233838/2sA3XMi33N#ade866d1-15d7-4b1a-b86f-8d5e437e792a
07/18/2024 08:05 AM
Apologies for late reply.
Yes I have checked and in addAccessRequest function the checksod flag is true.
07/18/2024 08:06 AM
Does issue resolved ?
07/18/2024 08:09 AM
No.
Same issue happening. SoD violation is triggering great in Saviynt platform, but not on ServiceNow end.
Raised a freshworks ticket and Saviynt team is looking into it. Will keep this forum posted when found the solution