Click HERE to see how Saviynt Intelligence is transforming the industry. |
09/02/2024 08:45 PM
Hello,
We have a use case wherein a user can request for a secondary account for self.
We were looking to have dynamic attributes to let user select from a dropdown the possible secondary accounts.
Kindly advise how Saviynt can handle secondary accounts as per best practices.
Thanks in advance,
Uzair
09/02/2024 09:01 PM
Hi @Uzair it is upto you how you want to manage it .. for us we created 2 different endpoint as we want to have a seperation between the two accounts.
09/02/2024 09:01 PM
09/02/2024 09:17 PM
@Uzair
Create separate endpoint / securitysystem/ connections.
Put in the filter at connection level and import accounts and entitlements as needed.
Any desired improvements or enhancements to this process, Saviynt encourages to submit your feedback through Saviynt's Ideas Portal at ideas.saviynt.com
Please notify here once the idea ticket has been created.
09/02/2024 10:39 PM
Hi @Uzair ,
If you don't want to have different ss/endpoints, your approach of having a dynamic attribute will work.
In update account JSON, you can if else condition based on that dynamic attribute. If new account requested then make a create account API call, else make update account API call.