v2021 Account Name Rule Evaluation For Rule Based Account Provisioning

[Community_User]

Originally posted on November 23 2021 at 16:46 UTC

We have Saviynt v2021 and observing an issue with the rule based account provisioning. For rule based provisioning, account name which are already reserved for pending tasks are not considered and new account tasks are generated with same duplicate account names. Let us know if this is known issue. Is there any fix for this available?

[Community_User]

Originally posted on November 23 2021 at 18:50 UTC

Hi Nitin,

When you say rules based Provisioning, do you mean Technical Rule ?

Can you provide more information on what you are doing ?

Regards,

Avinash Chhetri

[Community_User]

Originally posted on November 24 2021 at 03:43 UTC

Hi avinash,

Yes, access provisioning throw Technical Rule, account name which are already reserved for pending tasks are not considered and new account tasks are generated with same duplicate account names. that is the issue.

e.g. User A - Pending task 4004, User B -> Pending task - 4004 ideally next request should increase by 1.

[Community_User]

Originally posted on November 24 2021 at 05:48 UTC

Technical Rules ->> Assigning Enterprise Roles -> Enterprise role has entitlements. By default Saviynt application initiates New Account tasks. In this scenario duplicate account name is being used as uniqueness check against pending tasks is not considered in product.

[Community_User · Accepted solution]

Originally posted on November 24 2021 at 19:31 UTC

Hi Nitin,

As far as I know, I do not think Saviynt checks for inflight requests for account name validations.

Instead of Roles, even if you would request an account directly, it probably would behave in the same way, even if a task has been created.

Unless the task is completed and access provisioned or user already has an existing account, then the subsequent requests will trigger the account name rule validations.

Regards,

Avinash Chhetri