Best practices in implementing LDAP Directory Mapping for Transparent User Management

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PAM Self-Hosted Articles
13 min read
L0 Member
No ratings

Question

What are some best practices on implementing LDAP Directory Mapping for Transparent User Management?

Answer

Decide how users from LDAP Directory will be provisioned to logon to the Vault

  1. Assign special customized attribute to identify user as Cyber-Ark use
    This is the most effective way performance wise for implementation, but requires knowing and/or adding the attribute to the user object.
  2. Leverage the MemberOf attribute of the user object to identify user based on a Cyber-Ark group
    •  Create a group in LDAP directory where all members of the group will be allowed to log on to the Cyber-Ark Vault.This is more of a performance overhead compared to the first option because the Vault will have to look up the MemberOf attribut
      Note that Recursive group is not supported because recursive groups do not appear on MemberOf attribute
  3. Use an OU container and allow only the users that reside in a particular OU container to log on to the Cyber-Ark Vault
Please note that user accounts mapped from LDAP directory do not have the authorization to manage directory mapping in the Vault system.  Therefore, Vault Administrators will either need to create internal Vault account with "Manage Directory Mapping" authorization or leverage the built-in Administrator account in managing Directory Mapping.

Decide which Domain Controllers/LDAP Servers that the Cyber-Ark Vault Server will be able to query against.

Note that in Windows Active Directory, Global Catalog servers may not contain all the attributes of each user objects. For example, it does not contain the MemberOf attribute by default. Both the customized attribute and the MemberOf attribute options will require adding the attribute to the Global Catalogs for queries.

If your users and groups reside in multiple Domains/Forests, multiple Directory Profiles and bind accounts will be needed. The Vault supports multiple directories with multiple directory profiles. You may need to create multiple Directory Mappings for each Domain/Forest with specific LDAP filter queries in order to map the appropriate Users/Groups into the Vault system.

Review the requirements for setting up LDAP Directory Mapping

    • Active non-expiring directory “bind account” with privileges to read directory of users that will be integrated into Vault
    • Provide the fully Distinguished Name of the Bind User account and its credentials. (e.g. cn=abc,dc=xyz,dc=company,dc=com)
    • The Name of the LDAP Directory and Base Context (starting point of the directory search for users/groups)
    • DNS names and/or IP Addresses of the LDAP Server(s)
    • If SSL Connection from the Vault to the Directory is required (SLDAP), provide a Trusted Certificate that will be installed on the Vault servers
      • For SLDAP - Port 636/TCP (SSL LDAP) - Vault Servers | LDAP Server(s)
      • For LDAP - Port 389/TCP (Non-SSL LDAP) - Vault Servers | LDAP Server(s)

Decide if AD Domain Groups are going to be used for Authorization and Access Control for Safes Access

LDAP Groups can be mapped into the Vault to provision Safe Ownership access. For example, after the LDAP user accounts from the IT Security team and the LDAP security group for the IT Security team are created in the Vault via Directory Mapping, Vault Administrator can then give Safe ownership rights to either individual users or the entire  IT Security team group.  Members of the group will be able to access the Safe with the proper permissions.

When user logs on the Vault, Vault searches for the group in the directory based on the group's full DN and decide if the user is a member of the security group. Recursive Group can be enabled for role-based access but not recommended due to performance concern. The query will run on each and every group. Depending on number of groups in the LDAP directory, it may result in large queries and affect the log on time every time the user logs on.

Decide how often the background batch process on Vault server runs to query against LDAP to update users and groups attributes

User and Group details are retrieved from the external directory each time the user authenticates to the Vault based on the user/group DN. This query is based on the user DN of the user object and does not require a full LDAP scan of the existing Active Directory. 

An optional background batch job synchronizes existing external user objects with the External Directory to update the user information. It leverages the user DN of the accounts to perform the LDAP lookup. For example, there is a mapping for UserAccountDisabled=loginDisabled for Windows Activate Directory to mark the user account disabled.  The Vault will check the user status during user log on and disabled user will not be allowed to log on.  If the automatic deletion of users sync process is not enabled, the non-existent/non-matched users will not be deleted and they will not be allowed to log on.  If an external user that is not defined in the directory logs-on, you'll get an error.  However, you will not be able to locate these users (as no disable indication will be set).

The parameters of the background process are specified in DBParm.ini - offline schedule synchronize to check that all the users are updated in the directory, every search is in the scope of specific user.  The frequency of the offline schedule synchronize can be configured using intervals by the hour and can also be restricted to certain hours of the day.

Decide which authentication method(s) to authenticate users to the Vault

Every access to the Vault system has to be authenticated.  You can decide if you want to leverage Cyber-Ark Vault's embedded Password Authentication method (using Secure Remote Password Protocol) or leverage existing Enterprise Authentication methods.  During Directory Mapping, the only available authentication methods for users created automatically from LDAP (specified in the user template) are: RADIUS, PKI, NT Auth and LDAP. Therefore, you must enable one of them in the Vault level.

There are two primary end-user interfaces for Vault system access.  One is the PrivateArk Administrative Client (or PrivateArk Web Client, which is an ActiveX version of the full Client) and the other is Password Vault Web Access (PVWA).  The authentication method specified at the user template of the Directory Mapping determines the authentication method users must use when using the PrivateArk Administrative Client (w32 or ActiveX).

The authentication method specified at the Password Vault Web Access (PVWA) interface determines the authentication method users must use when using the PVWA.  You may want to consider using the same or different authentication method(s) when users are using the PrivateArk Administrative Client versus the Password Vault Web Access.  You may also have multiple different PVWA sites supporting different authentication methods.

The following authentication methods are supported:  LDAP, NT Authentication, Secure Remote Password Protocol (SRP), RSA SecurID, LDAP, RADIUS, PKI and various SSO solutions (via the PVWA).  You may depoly one or more of the above authentication methods.  Please refer to the Cyber-Ark Systems Requirements for details on supportability.

The type of Authentication method is not dependent on the type of LDAP Directory selected in Directory Mapping.  However, it is important to note that the username of the user account mapped from LDAP needs to match the username of the account that is being used for Authentication.  For example, you can map external users from Windows Active Directory domain while using RADIUS as the Authentication method for users to log onto the Vault system, given that the usernames in both Active Directory and RADIUS are exactly the same.  In this example, the Windows Active Directory is being used to provision logon authorization to the Vault while RADIUS is being used to authenticate the externally mapped AD user to access the Vault system.

Q: 
What are some best practices on implementing LDAP Directory Mapping for Transparent User Management?

A: 

Decide how users from LDAP Directory will be provisioned to logon to the Vault

  1. Assign special customized attribute to identify user as Cyber-Ark use
    This is the most effective way performance wise for implementation, but requires knowing and/or adding the attribute to the user object.
  2. Leverage the MemberOf attribute of the user object to identify user based on a Cyber-Ark group
    •  Create a group in LDAP directory where all members of the group will be allowed to log on to the Cyber-Ark Vault.This is more of a performance overhead compared to the first option because the Vault will have to look up the MemberOf attribut
      Note that Recursive group is not supported because recursive groups do not appear on MemberOf attribute
  3. Use an OU container and allow only the users that reside in a particular OU container to log on to the Cyber-Ark Vault
Please note that user accounts mapped from LDAP directory do not have the authorization to manage directory mapping in the Vault system.  Therefore, Vault Administrators will either need to create internal Vault account with "Manage Directory Mapping" authorization or leverage the built-in Administrator account in managing Directory Mapping.
 

Decide which Domain Controllers/LDAP Servers that the Cyber-Ark Vault Server will be able to query against.

Note that in Windows Active Directory, Global Catalog servers may not contain all the attributes of each user objects. For example, it does not contain the MemberOf attribute by default. Both the customized attribute and the MemberOf attribute options will require adding the attribute to the Global Catalogs for queries.

 

If your users and groups reside in multiple Domains/Forests, multiple Directory Profiles and bind accounts will be needed. The Vault supports multiple directories with multiple directory profiles. You may need to create multiple Directory Mappings for each Domain/Forest with specific LDAP filter queries in order to map the appropriate Users/Groups into the Vault system.

 

Review the requirements for setting up LDAP Directory Mapping

    • Active non-expiring directory “bind account” with privileges to read directory of users that will be integrated into Vault
    • Provide the fully Distinguished Name of the Bind User account and its credentials. (e.g. cn=abc,dc=xyz,dc=company,dc=com)
    • The Name of the LDAP Directory and Base Context (starting point of the directory search for users/groups)
    • DNS names and/or IP Addresses of the LDAP Server(s)
    • If SSL Connection from the Vault to the Directory is required (SLDAP), provide a Trusted Certificate that will be installed on the Vault servers
      • For SLDAP - Port 636/TCP (SSL LDAP) - Vault Servers | LDAP Server(s)
      • For LDAP - Port 389/TCP (Non-SSL LDAP) - Vault Servers | LDAP Server(s)

Decide if AD Domain Groups are going to be used for Authorization and Access Control for Safes Access

LDAP Groups can be mapped into the Vault to provision Safe Ownership access. For example, after the LDAP user accounts from the IT Security team and the LDAP security group for the IT Security team are created in the Vault via Directory Mapping, Vault Administrator can then give Safe ownership rights to either individual users or the entire  IT Security team group.  Members of the group will be able to access the Safe with the proper permissions.

 

When user logs on the Vault, Vault searches for the group in the directory based on the group's full DN and decide if the user is a member of the security group. Recursive Group can be enabled for role-based access but not recommended due to performance concern. The query will run on each and every group. Depending on number of groups in the LDAP directory, it may result in large queries and affect the log on time every time the user logs on.

 

Decide how often the background batch process on Vault server runs to query against LDAP to update users and groups attributes


User and Group details are retrieved from the external directory each time the user authenticates to the Vault based on the user/group DN. This query is based on the user DN of the user object and does not require a full LDAP scan of the existing Active Directory. 

An optional background batch job synchronizes existing external user objects with the External Directory to update the user information. It leverages the user DN of the accounts to perform the LDAP lookup. For example, there is a mapping for UserAccountDisabled=loginDisabled for Windows Activate Directory to mark the user account disabled.  The Vault will check the user status during user log on and disabled user will not be allowed to log on.  If the automatic deletion of users sync process is not enabled, the non-existent/non-matched users will not be deleted and they will not be allowed to log on.  If an external user that is not defined in the directory logs-on, you'll get an error.  However, you will not be able to locate these users (as no disable indication will be set).

The parameters of the background process are specified in DBParm.ini - offline schedule synchronize to check that all the users are updated in the directory, every search is in the scope of specific user.  The frequency of the offline schedule synchronize can be configured using intervals by the hour and can also be restricted to certain hours of the day.

Decide which authentication method(s) to authenticate users to the Vault

Every access to the Vault system has to be authenticated.  You can decide if you want to leverage Cyber-Ark Vault's embedded Password Authentication method (using Secure Remote Password Protocol) or leverage existing Enterprise Authentication methods.  During Directory Mapping, the only available authentication methods for users created automatically from LDAP (specified in the user template) are: RADIUS, PKI, NT Auth and LDAP. Therefore, you must enable one of them in the Vault level.

 

There are two primary end-user interfaces for Vault system access.  One is the PrivateArk Administrative Client (or PrivateArk Web Client, which is an ActiveX version of the full Client) and the other is Password Vault Web Access (PVWA).  The authentication method specified at the user template of the Directory Mapping determines the authentication method users must use when using the PrivateArk Administrative Client (w32 or ActiveX).

 

The authentication method specified at the Password Vault Web Access (PVWA) interface determines the authentication method users must use when using the PVWA.  You may want to consider using the same or different authentication method(s) when users are using the PrivateArk Administrative Client versus the Password Vault Web Access.  You may also have multiple different PVWA sites supporting different authentication methods.

The following authentication methods are supported:  LDAP, NT Authentication, Secure Remote Password Protocol (SRP), RSA SecurID, LDAP, RADIUS, PKI and various SSO solutions (via the PVWA).  You may depoly one or more of the above authentication methods.  Please refer to the Cyber-Ark Systems Requirements for details on supportability.

The type of Authentication method is not dependent on the type of LDAP Directory selected in Directory Mapping.  However, it is important to note that the username of the user account mapped from LDAP needs to match the username of the account that is being used for Authentication.  For example, you can map external users from Windows Active Directory domain while using RADIUS as the Authentication method for users to log onto the Vault system, given that the usernames in both Active Directory and RADIUS are exactly the same.  In this example, the Windows Active Directory is being used to provision logon authorization to the Vault while RADIUS is being used to authenticate the externally mapped AD user to access the Vault system.

Rate this article:
  • 22648 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎08-04-2020 09:54 AM
Updated by: