Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Rest connector Issue

yogendragautam
New Contributor II
New Contributor II

Hi,

Below is our requirement.

The createUser POST URL is:

https://{{host}}/auth/v1/companies/{{companyId}}/users

companyID is a dynamic attribute (single select)

Upon successful request, user gets the account for companyID "A".

Suppose, next time the same user modifies the account and selects companyID "B".

This time, we want to trigger a new account task and user should be provisioned to the same application with companyID B as well.

AccountName rule is users email.

8 REPLIES 8

AmitM
Valued Contributor
Valued Contributor

HI @yogendragautam ,

2 ways to do it :

1) If your has selected Modify existing account and changing B. Saviynt will only create Update account task. IN update account JSON , you can have a call to first check user exists and fetch existing company. If existing is same as new value thn update account call else create account call. How to choose url based on values is below

"url": "${(user.customproperty10=='ACC')?'https://graph.microsoft.com/v1.0/invitations':(user.customproperty10=='SSA')?'https://graph.microsof...':''}",

 

2) Easier solution would be that you allow New account request when account already exists in endpoint config. And let user request new account.

 

Thanks,

Amit

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

 

Hi,

If I allow requesting a new account, saviynt will not allow me to request for one since with the accountName rule being defined, No 2 accounts with the same name are allowed for the same endpoint.

Coming to suggestion 1: The check you have suggested is at user attribute level, but we are using dynamic attribute to select the companyId so it gets stored in the accounts custom property attribute. This I dont think works.

Any update on this ?

rushikeshvartak
All-Star
All-Star

You need to keep same json in create and Add Access JSON. for first time  create account json will be used next time onwards Add Access JSON


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Hi,

In Saviynt we are not allowed to have 2 same accountNames for the same endpoint.

The account Name rule is email for example.

I have provided my response, any update on it please ?

Hi @yogendragautam 

Could you please share the detailed business requirements for having two accounts with same account name in same endpoint. 

Regards,

Dhruv Sharma