Data store integrations
For user authentication, the SecureAuth® Identity Platform integrates with data stores (directories and databases) in your organization.
As an administrator, you define the data stores and directories from which to pull user data. User profiles remain in your data store and are never saved in the Identity Platform. This keeps data in your control with no duplicate content to manage elsewhere.
The following table lists the supported directory integrations in the New Experience for Identity Platform release 23.07 or later.
Cloud deployment | Hybrid/On-Prem deployment |
|---|---|
AD LDS ** | AD LDS |
ASP.NET ** | ASP.NET |
Active Directory (AD) ** | Active Directory (AD) |
Generic LDAP ** | Generic LDAP |
Identity Pool | Identity Pool |
Microsoft Entra ID (formerly Azure AD) | Microsoft Entra ID (formerly Azure AD) |
NetIQ eDirectory ** | NetIQ eDirectory |
— | OpenLDAP |
Oracle DB ** | Oracle DB |
SQL Server ** | SQL Server |
** Denotes that the SecureAuth Connector is required to communicate with the data store.
OpenLDAP is available in hybrid deployments only (release 26.1.0 or later).
When you add a data store and its mapping properties, the data store connection information is collectively saved as an object. This data store object is then associated with any number of policies and applications in the Identity Platform. This means you can associate multiple data stores with a single post authentication resource.
To see a list of profile field mapping properties and which profile properties are generated and stored in the SecureAuth cloud, see List of stored profile field properties.
Note
A data store added to the Identity Platform in the New Experience cannot be edited in the Advanced Settings.
Next steps
Add a data store. Some data stores in cloud deployments, require you to first install the SecureAuth Connector.