Click HERE to see how Saviynt Intelligence is transforming the industry. |
06/25/2024 10:44 PM
Hello,
We have a scenario where we need to create multiple account types (primary, secondary and privileged) for users under the same Active Directory Domain. These accounts will have different naming conventions.
What would be the best practice to implement this use case?
Should we need to create separate Connections, Security Systems and Endpoints? Or can we use single Connection, single Security System and multiple Endpoints?
Solved! Go to Solution.
06/25/2024 11:11 PM
Create separate endpoint / ss / connections
06/26/2024 10:19 AM
That means we need to create separate endpoint/ss/connections for each account?
For example -
for 1. primary account -> we need to create (endpoint, ss, connection)
for 2. secondary account -> we need to create (endpoint, ss, connection)
for 3. other privileged account -> we need to create (endpoint, ss, connection)
Thanks in advance.
06/26/2024 10:44 AM - edited 06/26/2024 10:45 AM
Yes
07/23/2024 06:28 AM
Hi @rushikeshvartak ,
This would result in importing the same access for all three security systems/endpoints, which is kind of a big overhead don't you think?
The second critical point is, that you have multiple application shown on the request start page, but in the end it would be only one application. Which makes the view a little bit confusing if you have the setup for different target applications.
The third thing which is uncertain for me, if the configuration of the Primary Account type on the endpoint. If only one account type can be support, how does this config make sense at all
I assume the better approach would be to remain with one application = endpoint, but this would need enhanced functionality of the form. For example, supporting by default different account types + naming conventions.
Do you know if this topic is addressed internally or is something in the pipeline like "bring your own form"?
Regards
Alex
07/23/2024 08:51 AM