and more in a single search tool across platforms. Read the announcement here. |
01/25/2024 11:53 AM
We have a requirement in our environment to use different approval workflows depending on the Endpoints for AD connected applications.
For example, some will use manager and resource owner approval while others require to have access approval on the entitlements owners.
Our understanding is that we need to add a new Active Directory Security System for each different use case. Is this a fair statement?
We did some testing around this and whenever we change the security system on an Endpoint, a new one gets created at the next AD access import job execution creating duplicate endpoints.
Does this mean we would also need to duplicate AD connexions to configure Endpoint mappings accordingly on each connexion depending on workflow requirements? It seems duplicating the Security System is not enough…
Is there another (maybe simpler) way of achieving this?
I suppose we are not the only ones with such requirements.
Thank you in advance for the feedback!
Solved! Go to Solution.
01/25/2024 12:54 PM
01/29/2024 05:05 AM
Thank you rushikeshvartak.
I will give this a try. It does make sense and it seems simpler than having multiple security systems and connexions.