<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Best practices in implementing LDAP Directory Mapping for Transparent User Management in PAM Self-Hosted Articles</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/best-practices-in-implementing-ldap-directory-mapping-for/ta-p/1430111</link>
    <description>&lt;H3&gt;Question&lt;/H3&gt;
&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;Wh&lt;/SPAN&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;at are some best practices on implementing LDAP Directory Mapping for Transparent User Management?&lt;/SPAN&gt;
&lt;H3&gt;Answer&lt;/H3&gt;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;Decide how users from LDAP Directory will be provisioned to logon to the Vault&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;OL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;Assign special customized attribute to identify user as Cyber-Ark use&lt;/SPAN&gt;&lt;BR /&gt; &lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;This is the most effective way performance wise for implementation, but requires knowing and/or adding the attribute to the user object.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;Leverage the MemberOf attribute of the&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt; user object to identify user based on a Cyber-Ark group&lt;/SPAN&gt;
&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Symbol;"&gt;&lt;SPAN&gt;&lt;SPAN style="font-weight: normal;font-size: 7pt;font-style: normal;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Create a group in LDAP directory where all members of the group will be allowed to log on to the Cyber-Ark Vault.&lt;/SPAN&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;This is more of a performance overhead compared to the first option because the Vault will have to look up the &lt;SPAN style="font-style: italic;"&gt;MemberOf&lt;/SPAN&gt; attribut&lt;/SPAN&gt;&lt;BR /&gt; &lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Note that Recursive group is not supported because recursive groups do not appear on &lt;SPAN style="font-style: italic;"&gt;MemberOf&lt;/SPAN&gt; attribute&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Use an OU container and allow only the users that reside in a particular OU container to log on to the Cyber-Ark Vault&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;SPAN style="font-size: 10pt;font-family: Verdana,Helvetica,Sans-Serif;"&gt;Please note that user accounts mapped from LDAP directory do not have the authorization to manage directory mapping in the Vault system.&amp;nbsp; 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.&lt;/SPAN&gt;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Decide which Domain Controllers/LDAP Servers that the Cyber-Ark Vault Server will be able to query against.&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;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 &lt;SPAN style="font-style: italic;"&gt;MemberOf&lt;/SPAN&gt; attribute by default. Both the customized attribute and the &lt;SPAN style="font-style: italic;"&gt;MemberOf &lt;/SPAN&gt;attribute options will require adding the attribute to the Global Catalogs for queries.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;If your users and groups reside in multiple Domains/Forests, multiple Directory Profiles and bind accounts will be needed.&lt;SPAN&gt; &lt;/SPAN&gt;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.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Review the requirements for setting up LDAP Directory Mapping&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;
&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana,Helvetica,Sans-Serif;"&gt;Active non-expiring directory “bind account” with privileges to read directory of users that will be integrated into Vault&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;Provide the fully &lt;B&gt;Distinguished Name&lt;/B&gt; of the Bind User account and its credentials. (e.g. cn=abc,dc=xyz,dc=company,dc=com)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;The Name of the LDAP Directory and Base Context (starting point of the directory search for users/groups)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;DNS names and/or IP Addresses of the LDAP Server(s)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;If SSL Connection from the Vault to the Directory is required (SLDAP), provide a Trusted Certificate that will be installed on the Vault servers&lt;/SPAN&gt;
&lt;UL style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;For SLDAP - Port &lt;B&gt;636/TCP (SSL LDAP)&lt;/B&gt; - Vault Servers | LDAP Server(s)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;For LDAP - Port &lt;B&gt;389/TCP (Non-SSL LDAP)&lt;/B&gt; - Vault Servers | LDAP Server(s)&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Decide if AD Domain Groups are going to be used for Authorization and Access Control for Safes Access&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;LDAP Groups can be mapped into the Vault to provision Safe Ownership access.&lt;SPAN&gt; &lt;/SPAN&gt;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&amp;nbsp; IT Security team group.&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;Members of the group will be able to access the Safe with the proper permissions. &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;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.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;&lt;SPAN style="font-weight: bold;"&gt;Decide how often the background batch process on Vault server runs to query against LDAP to update users and groups attributes&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;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.&amp;nbsp; &lt;/SPAN&gt;&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;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.&amp;nbsp; The Vault will check the user status during user log on and disabled user will not be allowed to log on.&amp;nbsp; 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.&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;If an external user that is not defined in the directory logs-on, you'll get an error.&amp;nbsp; However, you will not be able to locate these users (as no disable indication will be set).&lt;/SPAN&gt;&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;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.&amp;nbsp; 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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;&lt;SPAN style="font-weight: bold;"&gt;Decide which authentication method(s) to authenticate users to the Vault&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;Every access to the Vault system has to be authenticated.&amp;nbsp; 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.&amp;nbsp;&amp;nbsp;During Directory Mapping, the&lt;SPAN&gt;&amp;nbsp;only available authentication methods for users created automatically from LDAP (specified in the user&amp;nbsp;template) are: RADIUS, PKI, NT Auth and LDAP. Therefore, you must enable one of them in the Vault level.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;There are two&amp;nbsp;primary end-user interfaces for Vault system access.&amp;nbsp; 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).&amp;nbsp;&amp;nbsp;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).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;The authentication method specified at the&amp;nbsp;Password Vault Web Access (PVWA) interface determines the authentication method users must use when using the PVWA.&amp;nbsp; 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.&amp;nbsp; You may also have multiple different PVWA sites supporting different authentication methods.&lt;BR /&gt;&lt;BR /&gt;The following authentication methods are supported:&amp;nbsp; LDAP, NT Authentication, Secure Remote Password Protocol (SRP), RSA SecurID, LDAP, RADIUS, PKI and various SSO solutions (via the PVWA).&amp;nbsp; You may depoly one or more of the above authentication methods.&amp;nbsp; Please refer to the Cyber-Ark Systems Requirements for details on supportability.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;The type of Authentication method is not dependent on the type of LDAP Directory selected in Directory Mapping.&amp;nbsp; 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.&amp;nbsp; 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.&amp;nbsp; 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.&lt;/SPAN&gt;&lt;/P&gt;
&lt;SPAN style="font-weight: bold;font-family: Verdana,Helvetica,Sans-Serif;text-decoration: underline;"&gt;Q&lt;/SPAN&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;:&amp;nbsp; &lt;/SPAN&gt;&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;What are some best practices on implementing LDAP Directory Mapping for Transparent User Management?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: bold;text-decoration: underline;"&gt;A&lt;/SPAN&gt;:&amp;nbsp;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;Decide how users from LDAP Directory will be provisioned to logon to the Vault&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;OL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;Assign special customized attribute to identify user as Cyber-Ark use&lt;/SPAN&gt;&lt;BR /&gt; &lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;This is the most effective way performance wise for implementation, but requires knowing and/or adding the attribute to the user object.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;Leverage the MemberOf attribute of the&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt; user object to identify user based on a Cyber-Ark group&lt;/SPAN&gt;
&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Symbol;"&gt;&lt;SPAN&gt;&lt;SPAN style="font-weight: normal;font-size: 7pt;font-style: normal;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Create a group in LDAP directory where all members of the group will be allowed to log on to the Cyber-Ark Vault.&lt;/SPAN&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;This is more of a performance overhead compared to the first option because the Vault will have to look up the &lt;SPAN style="font-style: italic;"&gt;MemberOf&lt;/SPAN&gt; attribut&lt;/SPAN&gt;&lt;BR /&gt; &lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Note that Recursive group is not supported because recursive groups do not appear on &lt;SPAN style="font-style: italic;"&gt;MemberOf&lt;/SPAN&gt; attribute&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Use an OU container and allow only the users that reside in a particular OU container to log on to the Cyber-Ark Vault&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;SPAN style="font-size: 10pt;font-family: Verdana,Helvetica,Sans-Serif;"&gt;Please note that user accounts mapped from LDAP directory do not have the authorization to manage directory mapping in the Vault system.&amp;nbsp; 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.&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Decide which Domain Controllers/LDAP Servers that the Cyber-Ark Vault Server will be able to query against.&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;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 &lt;SPAN style="font-style: italic;"&gt;MemberOf&lt;/SPAN&gt; attribute by default. Both the customized attribute and the &lt;SPAN style="font-style: italic;"&gt;MemberOf &lt;/SPAN&gt;attribute options will require adding the attribute to the Global Catalogs for queries.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;If your users and groups reside in multiple Domains/Forests, multiple Directory Profiles and bind accounts will be needed.&lt;SPAN&gt; &lt;/SPAN&gt;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.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Review the requirements for setting up LDAP Directory Mapping&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;
&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana,Helvetica,Sans-Serif;"&gt;Active non-expiring directory “bind account” with privileges to read directory of users that will be integrated into Vault&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;Provide the fully &lt;B&gt;Distinguished Name&lt;/B&gt; of the Bind User account and its credentials. (e.g. cn=abc,dc=xyz,dc=company,dc=com)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;The Name of the LDAP Directory and Base Context (starting point of the directory search for users/groups)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;DNS names and/or IP Addresses of the LDAP Server(s)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;If SSL Connection from the Vault to the Directory is required (SLDAP), provide a Trusted Certificate that will be installed on the Vault servers&lt;/SPAN&gt;
&lt;UL style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;For SLDAP - Port &lt;B&gt;636/TCP (SSL LDAP)&lt;/B&gt; - Vault Servers | LDAP Server(s)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;For LDAP - Port &lt;B&gt;389/TCP (Non-SSL LDAP)&lt;/B&gt; - Vault Servers | LDAP Server(s)&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Decide if AD Domain Groups are going to be used for Authorization and Access Control for Safes Access&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;LDAP Groups can be mapped into the Vault to provision Safe Ownership access.&lt;SPAN&gt; &lt;/SPAN&gt;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&amp;nbsp; IT Security team group.&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;Members of the group will be able to access the Safe with the proper permissions. &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;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.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;&lt;SPAN style="font-weight: bold;"&gt;Decide how often the background batch process on Vault server runs to query against LDAP to update users and groups attributes&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;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.&amp;nbsp; &lt;/SPAN&gt;&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;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.&amp;nbsp; The Vault will check the user status during user log on and disabled user will not be allowed to log on.&amp;nbsp; 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.&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;If an external user that is not defined in the directory logs-on, you'll get an error.&amp;nbsp; However, you will not be able to locate these users (as no disable indication will be set).&lt;/SPAN&gt;&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;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.&amp;nbsp; 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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;&lt;SPAN style="font-weight: bold;"&gt;Decide which authentication method(s) to authenticate users to the Vault&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;Every access to the Vault system has to be authenticated.&amp;nbsp; 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.&amp;nbsp;&amp;nbsp;During Directory Mapping, the&lt;SPAN&gt;&amp;nbsp;only available authentication methods for users created automatically from LDAP (specified in the user&amp;nbsp;template) are: RADIUS, PKI, NT Auth and LDAP. Therefore, you must enable one of them in the Vault level.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;There are two&amp;nbsp;primary end-user interfaces for Vault system access.&amp;nbsp; 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).&amp;nbsp;&amp;nbsp;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).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;The authentication method specified at the&amp;nbsp;Password Vault Web Access (PVWA) interface determines the authentication method users must use when using the PVWA.&amp;nbsp; 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.&amp;nbsp; You may also have multiple different PVWA sites supporting different authentication methods.&lt;BR /&gt;&lt;BR /&gt;The following authentication methods are supported:&amp;nbsp; LDAP, NT Authentication, Secure Remote Password Protocol (SRP), RSA SecurID, LDAP, RADIUS, PKI and various SSO solutions (via the PVWA).&amp;nbsp; You may depoly one or more of the above authentication methods.&amp;nbsp; Please refer to the Cyber-Ark Systems Requirements for details on supportability.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;The type of Authentication method is not dependent on the type of LDAP Directory selected in Directory Mapping.&amp;nbsp; 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.&amp;nbsp; 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.&amp;nbsp; 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.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 04 Aug 2020 16:54:09 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2020-08-04T16:54:09Z</dc:date>
    <item>
      <title>Best practices in implementing LDAP Directory Mapping for Transparent User Management</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/best-practices-in-implementing-ldap-directory-mapping-for/ta-p/1430111</link>
      <description>&lt;H3&gt;Question&lt;/H3&gt;
&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;Wh&lt;/SPAN&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;at are some best practices on implementing LDAP Directory Mapping for Transparent User Management?&lt;/SPAN&gt;
&lt;H3&gt;Answer&lt;/H3&gt;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;Decide how users from LDAP Directory will be provisioned to logon to the Vault&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;OL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;Assign special customized attribute to identify user as Cyber-Ark use&lt;/SPAN&gt;&lt;BR /&gt; &lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;This is the most effective way performance wise for implementation, but requires knowing and/or adding the attribute to the user object.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;Leverage the MemberOf attribute of the&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt; user object to identify user based on a Cyber-Ark group&lt;/SPAN&gt;
&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Symbol;"&gt;&lt;SPAN&gt;&lt;SPAN style="font-weight: normal;font-size: 7pt;font-style: normal;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Create a group in LDAP directory where all members of the group will be allowed to log on to the Cyber-Ark Vault.&lt;/SPAN&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;This is more of a performance overhead compared to the first option because the Vault will have to look up the &lt;SPAN style="font-style: italic;"&gt;MemberOf&lt;/SPAN&gt; attribut&lt;/SPAN&gt;&lt;BR /&gt; &lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Note that Recursive group is not supported because recursive groups do not appear on &lt;SPAN style="font-style: italic;"&gt;MemberOf&lt;/SPAN&gt; attribute&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Use an OU container and allow only the users that reside in a particular OU container to log on to the Cyber-Ark Vault&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;SPAN style="font-size: 10pt;font-family: Verdana,Helvetica,Sans-Serif;"&gt;Please note that user accounts mapped from LDAP directory do not have the authorization to manage directory mapping in the Vault system.&amp;nbsp; 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.&lt;/SPAN&gt;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Decide which Domain Controllers/LDAP Servers that the Cyber-Ark Vault Server will be able to query against.&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;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 &lt;SPAN style="font-style: italic;"&gt;MemberOf&lt;/SPAN&gt; attribute by default. Both the customized attribute and the &lt;SPAN style="font-style: italic;"&gt;MemberOf &lt;/SPAN&gt;attribute options will require adding the attribute to the Global Catalogs for queries.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;If your users and groups reside in multiple Domains/Forests, multiple Directory Profiles and bind accounts will be needed.&lt;SPAN&gt; &lt;/SPAN&gt;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.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Review the requirements for setting up LDAP Directory Mapping&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;
&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana,Helvetica,Sans-Serif;"&gt;Active non-expiring directory “bind account” with privileges to read directory of users that will be integrated into Vault&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;Provide the fully &lt;B&gt;Distinguished Name&lt;/B&gt; of the Bind User account and its credentials. (e.g. cn=abc,dc=xyz,dc=company,dc=com)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;The Name of the LDAP Directory and Base Context (starting point of the directory search for users/groups)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;DNS names and/or IP Addresses of the LDAP Server(s)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;If SSL Connection from the Vault to the Directory is required (SLDAP), provide a Trusted Certificate that will be installed on the Vault servers&lt;/SPAN&gt;
&lt;UL style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;For SLDAP - Port &lt;B&gt;636/TCP (SSL LDAP)&lt;/B&gt; - Vault Servers | LDAP Server(s)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;For LDAP - Port &lt;B&gt;389/TCP (Non-SSL LDAP)&lt;/B&gt; - Vault Servers | LDAP Server(s)&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Decide if AD Domain Groups are going to be used for Authorization and Access Control for Safes Access&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;LDAP Groups can be mapped into the Vault to provision Safe Ownership access.&lt;SPAN&gt; &lt;/SPAN&gt;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&amp;nbsp; IT Security team group.&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;Members of the group will be able to access the Safe with the proper permissions. &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;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.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;&lt;SPAN style="font-weight: bold;"&gt;Decide how often the background batch process on Vault server runs to query against LDAP to update users and groups attributes&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;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.&amp;nbsp; &lt;/SPAN&gt;&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;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.&amp;nbsp; The Vault will check the user status during user log on and disabled user will not be allowed to log on.&amp;nbsp; 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.&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;If an external user that is not defined in the directory logs-on, you'll get an error.&amp;nbsp; However, you will not be able to locate these users (as no disable indication will be set).&lt;/SPAN&gt;&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;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.&amp;nbsp; 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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;&lt;SPAN style="font-weight: bold;"&gt;Decide which authentication method(s) to authenticate users to the Vault&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;Every access to the Vault system has to be authenticated.&amp;nbsp; 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.&amp;nbsp;&amp;nbsp;During Directory Mapping, the&lt;SPAN&gt;&amp;nbsp;only available authentication methods for users created automatically from LDAP (specified in the user&amp;nbsp;template) are: RADIUS, PKI, NT Auth and LDAP. Therefore, you must enable one of them in the Vault level.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;There are two&amp;nbsp;primary end-user interfaces for Vault system access.&amp;nbsp; 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).&amp;nbsp;&amp;nbsp;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).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;The authentication method specified at the&amp;nbsp;Password Vault Web Access (PVWA) interface determines the authentication method users must use when using the PVWA.&amp;nbsp; 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.&amp;nbsp; You may also have multiple different PVWA sites supporting different authentication methods.&lt;BR /&gt;&lt;BR /&gt;The following authentication methods are supported:&amp;nbsp; LDAP, NT Authentication, Secure Remote Password Protocol (SRP), RSA SecurID, LDAP, RADIUS, PKI and various SSO solutions (via the PVWA).&amp;nbsp; You may depoly one or more of the above authentication methods.&amp;nbsp; Please refer to the Cyber-Ark Systems Requirements for details on supportability.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;The type of Authentication method is not dependent on the type of LDAP Directory selected in Directory Mapping.&amp;nbsp; 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.&amp;nbsp; 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.&amp;nbsp; 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.&lt;/SPAN&gt;&lt;/P&gt;
&lt;SPAN style="font-weight: bold;font-family: Verdana,Helvetica,Sans-Serif;text-decoration: underline;"&gt;Q&lt;/SPAN&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;:&amp;nbsp; &lt;/SPAN&gt;&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;What are some best practices on implementing LDAP Directory Mapping for Transparent User Management?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: bold;text-decoration: underline;"&gt;A&lt;/SPAN&gt;:&amp;nbsp;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;Decide how users from LDAP Directory will be provisioned to logon to the Vault&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;OL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;Assign special customized attribute to identify user as Cyber-Ark use&lt;/SPAN&gt;&lt;BR /&gt; &lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;This is the most effective way performance wise for implementation, but requires knowing and/or adding the attribute to the user object.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Verdana;"&gt;Leverage the MemberOf attribute of the&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt; user object to identify user based on a Cyber-Ark group&lt;/SPAN&gt;
&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;color: black;font-family: Symbol;"&gt;&lt;SPAN&gt;&lt;SPAN style="font-weight: normal;font-size: 7pt;font-style: normal;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Create a group in LDAP directory where all members of the group will be allowed to log on to the Cyber-Ark Vault.&lt;/SPAN&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;This is more of a performance overhead compared to the first option because the Vault will have to look up the &lt;SPAN style="font-style: italic;"&gt;MemberOf&lt;/SPAN&gt; attribut&lt;/SPAN&gt;&lt;BR /&gt; &lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Note that Recursive group is not supported because recursive groups do not appear on &lt;SPAN style="font-style: italic;"&gt;MemberOf&lt;/SPAN&gt; attribute&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Use an OU container and allow only the users that reside in a particular OU container to log on to the Cyber-Ark Vault&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;SPAN style="font-size: 10pt;font-family: Verdana,Helvetica,Sans-Serif;"&gt;Please note that user accounts mapped from LDAP directory do not have the authorization to manage directory mapping in the Vault system.&amp;nbsp; 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.&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Decide which Domain Controllers/LDAP Servers that the Cyber-Ark Vault Server will be able to query against.&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;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 &lt;SPAN style="font-style: italic;"&gt;MemberOf&lt;/SPAN&gt; attribute by default. Both the customized attribute and the &lt;SPAN style="font-style: italic;"&gt;MemberOf &lt;/SPAN&gt;attribute options will require adding the attribute to the Global Catalogs for queries.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;If your users and groups reside in multiple Domains/Forests, multiple Directory Profiles and bind accounts will be needed.&lt;SPAN&gt; &lt;/SPAN&gt;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.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Review the requirements for setting up LDAP Directory Mapping&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;
&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana,Helvetica,Sans-Serif;"&gt;Active non-expiring directory “bind account” with privileges to read directory of users that will be integrated into Vault&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;Provide the fully &lt;B&gt;Distinguished Name&lt;/B&gt; of the Bind User account and its credentials. (e.g. cn=abc,dc=xyz,dc=company,dc=com)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;The Name of the LDAP Directory and Base Context (starting point of the directory search for users/groups)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;DNS names and/or IP Addresses of the LDAP Server(s)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;If SSL Connection from the Vault to the Directory is required (SLDAP), provide a Trusted Certificate that will be installed on the Vault servers&lt;/SPAN&gt;
&lt;UL style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;For SLDAP - Port &lt;B&gt;636/TCP (SSL LDAP)&lt;/B&gt; - Vault Servers | LDAP Server(s)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;For LDAP - Port &lt;B&gt;389/TCP (Non-SSL LDAP)&lt;/B&gt; - Vault Servers | LDAP Server(s)&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;&lt;B&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;Decide if AD Domain Groups are going to be used for Authorization and Access Control for Safes Access&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;LDAP Groups can be mapped into the Vault to provision Safe Ownership access.&lt;SPAN&gt; &lt;/SPAN&gt;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&amp;nbsp; IT Security team group.&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;Members of the group will be able to access the Safe with the proper permissions. &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;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.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;&lt;SPAN style="font-weight: bold;"&gt;Decide how often the background batch process on Vault server runs to query against LDAP to update users and groups attributes&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;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.&amp;nbsp; &lt;/SPAN&gt;&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;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.&amp;nbsp; The Vault will check the user status during user log on and disabled user will not be allowed to log on.&amp;nbsp; 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.&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;If an external user that is not defined in the directory logs-on, you'll get an error.&amp;nbsp; However, you will not be able to locate these users (as no disable indication will be set).&lt;/SPAN&gt;&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;BR style="font-family: Verdana,Helvetica,Sans-Serif;" /&gt;
&lt;SPAN style="font-family: Verdana,Helvetica,Sans-Serif;"&gt;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.&amp;nbsp; 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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;&lt;SPAN style="font-weight: bold;"&gt;Decide which authentication method(s) to authenticate users to the Vault&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;Every access to the Vault system has to be authenticated.&amp;nbsp; 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.&amp;nbsp;&amp;nbsp;During Directory Mapping, the&lt;SPAN&gt;&amp;nbsp;only available authentication methods for users created automatically from LDAP (specified in the user&amp;nbsp;template) are: RADIUS, PKI, NT Auth and LDAP. Therefore, you must enable one of them in the Vault level.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;There are two&amp;nbsp;primary end-user interfaces for Vault system access.&amp;nbsp; 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).&amp;nbsp;&amp;nbsp;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).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;The authentication method specified at the&amp;nbsp;Password Vault Web Access (PVWA) interface determines the authentication method users must use when using the PVWA.&amp;nbsp; 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.&amp;nbsp; You may also have multiple different PVWA sites supporting different authentication methods.&lt;BR /&gt;&lt;BR /&gt;The following authentication methods are supported:&amp;nbsp; LDAP, NT Authentication, Secure Remote Password Protocol (SRP), RSA SecurID, LDAP, RADIUS, PKI and various SSO solutions (via the PVWA).&amp;nbsp; You may depoly one or more of the above authentication methods.&amp;nbsp; Please refer to the Cyber-Ark Systems Requirements for details on supportability.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt;font-family: Verdana;"&gt;The type of Authentication method is not dependent on the type of LDAP Directory selected in Directory Mapping.&amp;nbsp; 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.&amp;nbsp; 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.&amp;nbsp; 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.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Aug 2020 16:54:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/best-practices-in-implementing-ldap-directory-mapping-for/ta-p/1430111</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2020-08-04T16:54:09Z</dc:date>
    </item>
  </channel>
</rss>

