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

Creating logical applications for Active Directory

kunal_saxena
Regular Contributor
Regular Contributor

Hi,

We have integrated an active directory domain with our Saviynt environment. We have few applications for which access is granted through AD groups and we want to create separate endpoints for these applications in Saviynt. For this, we are planning to take the following steps:

  • Use the ENDPOINT_FILTER configuration under AD connection to define the groups used by each application
  • Create application endpoints and associate them to the AD security system
  • Modify the workflow to accommodate and approvals required for these application
  • Run the AD account import job to import accounts and entitlements under these applications.

However this documentation for logical apps mentions that we should create a separate connection and security system. Also, to create a endpoint for Parent application.

kunal_saxena_0-1719826970776.pngkunal_saxena_1-1719826986759.png

Can you please let us know which approach will be more feasible for our requirements? The one we have listed above or the one in documentation?

If it is the documented approach, then what is the benefit of creating a new connection and security system?

Thanks,
Kunal

3 REPLIES 3

NM
Valued Contributor
Valued Contributor

@kunal_saxena , you don't have to create a seperate SS or connection for logical application.

Manu269
All-Star
All-Star

@kunal_saxena the document talks more about in terms of management.

The one you are working on is also correct.

We are using the same.

Regards
Manish Kumar
If the response answered your query, please Accept As Solution and Kudos
.

rushikeshvartak
All-Star
All-Star
  • For Filtering applications from technical to logical application 1-1-N is approach 
  • one connection - 1 security system and multiple endpoints
  • Documentation specifications are more about naming conventions for ease of use.

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