Add AD LDS data store
In the SecureAuth® Identity Platform, you can add an Active Directory Lightweight Directory Services (AD LDS) data store to assert or manage user identity information.
Prerequisites
Identity Platform release 23.07, cloud or hybrid deployment
SecureAuth Connector installed and connected for Identity Platform cloud deployment
Active Directory Lightweight Directory Services (AD LDS) data store
Process
There are two parts to adding a data store in the Identity Platform — (1) adding the data store and (2) mapping the data store properties.
Step 1 of 2: Add an AD LDS data store
The first part of adding an AD LDS data store is configuring the data store name, connections, credentials, and search attributes.
On the left side of the Identity Platform page, click Data Stores.
Select the Data Stores tab.
Click Add a Data Store.
On the Add a Data Store page, start with the following configurations, depending on your deployment type.
Settings in hybrid deployments
Settings in cloud deployments
Data Store Name
Set the name of the data store.
Connection Type
Set to Lightweight Directory Services (AD-LDS).
Use this directory for user membership validation
Appears only in hybrid deployments
Use one of the following options:
On – Enable membership validation; use the directory to search for the user's membership in a user group.
This means the directory is a Membership Store, containing the password to validate with the username.
After the data store is saved, this field is the Membership Store label shown on the View Summary.
A common use case for a Membership Store would be to have a directory with username and password information (and maybe some profile information), and then have a second directory or database used to store and access data that the Identity Platform writes to the directory (such as device recognition, device enrollment, push notification tokens, and so on).
Off – Disable membership validation; use the directory to search only for the user profile information.
This means the directory is only used to find the username and profile information (such as phone number, email address, device recognition profiles, OATH tokens, and so on).
Group of connectors
Appears only in cloud deployments
Assign this data store to a SecureAuth Connector group.
To learn more about Connector groups, see Manage SecureAuth Connector groups.
In the Connection String section, set the connection string for the domain to the AD LDS data store.
Note
For information about how to identify the corporate connection string, see the external article How can I figure out my LDAP connection string?
Source Domain
The domain for your directory to build the connection string in the next field.
For example:
acme.comConnection String
The value in this field is the connection string auto-populated by the Source Domain field and contains domain and generic values for DC=directory, DC=domain, unless a custom connection string is manually entered.
For example, the result would be:
LDAP://acme.com/DC=acme,DC=comadvanced mode
To manually enter the connection string, click the advanced mode link.
In the Credentials section, provide the log in credentials to access the AD LDS data store.
Enter Service Account Credentials
With this option selected, enter the following fields:
Service Account Login – Email address for the service account login
Password – Password for the service account login
Test the data store connection by clicking Test Credentials.
Use CyberArk Vault for Credentials
With this option, enter at least one field for the service account login:
Username – User name of the machine to be scanned by CyberArk's Application Identity Manager (AIM). This information appears on the Account Details page of the CyberArk Password Vault Web Access (PVWA) Admin Console
Address – Address of machine to be scanned by AIM
Safe – Name of Access Control Safe where credentials are stored
Folder – Name of folder where account resides (by default, it its the root folder)
Object – Unique identifier Object name for the account
Service account passwords stored on the CyberArk Vault are automatically populated. These are not stored in SecureAuth® Identity Platform.
Test the data store connection by clicking Test Credentials.
In the Search Filter section, define the search attribute to find a user account.
Search Attribute
Set the search attribute.
Available options are cn, uid, sAMAccountName, or userPrincipalName (UPN).
Search Filter
Value is auto-populated in this field.
Example search filters for each search attribute type are:
cn:
(&(cn=%v)(objectclass=*))uid:
(&(uid=%v)(objectclass=inetOrgPerson))sAMAccountName:
(&(sAMAccountName=%v)(objectclass=*))userPrincipalName (UPN):
(&(userPrincipalName=%v)(objectclass=user)(objectcategory=person))
advanced mode
To enter a custom search filter, click the advanced mode link.
In the Advanced Settings section, define the attribute to encrypt user profile data.
Validate User Type
Choose how to validate usernames and passwords in AD LDS:
Bind – Make a direct call to the directory to validate the username and password (faster search)
Search – Use the search function to find and validate a username and password (slower search)
Connection Mode
Select how the Identity Platform and the directory connect:
Secure – Use a secure LDAP connection on Port 389, using NTLMv2
SSL – Use a secure connection on Port 636, but uses Secure Socket Layer technology, which relies on certificates
Standard – Use a standard LDAP connection on Port 389 that uses basic authentication (plain text)
Allow Anonymous Queries
Move the slider to indicate whether non-authenticated users should also be granted access to browse the protected resource.
In most cases, this setting should be off; unless using a generic LDAP directory.
Allow Advanced User Checks
Move the slider to indicate whether to allow the Identity Platform to search this directory for more user information. This is useful in a scenario in which a user account is locked.
Disable Nested Groups
Move this slider ON to indicate that the Identity Platform will only search main group memberships and ignore nested groups.
This will improve performance.
Click Continue.
The Map Data Store Properties page opens.
Step 2 of 2: Map the AD LDS data store properties
The second part of adding an AD LDS data store is mapping the data store properties.
Each user is uniquely identified by profile data that is read from or stored in your directories and databases.
The Identity Platform does not store user profiles, so your organizational directory attributes must be mapped to AD LDS profile properties to be read and updated in the directory by the Identity Platform. The directory attribute mapped to the property is retrieved only when required for authentication or assertion purposes.
For more information about how data store profile properties are stored for on-premises, hybrid, or cloud Identity Platform deployments, see List of stored profile field properties.
Note
Each mapped profile property should have its own directory attribute. It is not recommended to map the same directory attribute to more than one property.
For example, the mobile attribute is mapped to Phone 2, so you would use a different attribute for Phone 3.
On the Map Data Stores Properties page, define the required attributes in the Active Directory Field that corresponds to each AD LDS property required by your environment and the Identity Platform. The required attributes are:
First Name
Last Name
Groups
Email 1 (Work)
Define the recommended attribute in the Active Directory Field that correspond to each AD LDS property. The recommended attributes are:
Phone 1 (Work)
Phone 2 (Mobile)
In the Writable column, define whether a profile property can be writable (select check box) or not writable (cleared check box) according to your AD LDS configuration.
For example, if you want to allow users to update their personal email address on the self-services page, select the Writable check box.
Some profile properties are disabled by default in the system; for example, biometric profile properties used by SecureAuth cloud services.
For mapped profile properties (for example, Push Notification Tokens, Behavioral Biometrics, and Device Profiles), specify the Data Format to define how data is encrypted and stored in the directory.
For cloud deployments, certain profile properties (for example, Push Notification Tokens, Behavioral Biometrics, and Device Profiles) are generated and used by SecureAuth, and stored in the SecureAuth cloud database.
The selection options are listed below (options vary depending on your Identity Platform deployment):
plain text – store data as regular, readable text (default)
standard encryption – store and encrypt data using RSA encryption
advanced encryption – store and encrypt data using AES encryption
standard hash – store and encrypt data using SHA-256 hash
plain binary – store data as a binary representation of the data (uses a .NET library to make it binary – may not be readable by all applications)
json – store data in a universal format, readable by all applications (similar to plain text)
encrypted json – stored as JSON, with values inside encrypted using AES encryption
For a complete list of fields for the available stored profiles, see the List of stored profile fields.
Click Save Data Store.
The AD LDS data store you just added appears in the User Data Stores list.