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 22.12 or later.
Cloud deployment | Hybrid deployment |
|---|---|
ASP.NET DB ** 1 | ASP.NET DB 1 |
Active Directory (AD) ** | Active Directory (AD) |
Generic LDAP ** | Generic LDAP |
Microsoft Entra ID (formerly Azure AD) | Microsoft Entra ID (formerly Azure AD) |
NetIQ eDirectory ** | NetIQ eDirectory |
Oracle DB ** | Oracle DB |
SQL Server ** | SQL Server |
** Denotes that the SecureAuth Connector is required to communicate with the data store.
1 Available in Identity Platform 22.12 with hotfix 22.12-2 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.
Prerequisites
SecureAuth® Identity Platform release 22.12 or later
Data store supported in the New Experience for cloud or hybrid deployments
Service account set up for the Identity Platform to access the data store. The service account must be granted read privileges and optional write privileges to update user information.
For Identity Platform cloud deployments, the SecureAuth Connector must be installed to establish communication between the data store on a local server in your organization and the Identity Platform
Note
To migrate from SecureAuth IdP (on-prem) version 9.3 with an existing AD data store configured using the New Experience to the Identity Platform (cloud), you will need to reenter the data store credentials after downloading and installing the SecureAuth Connector.
Next steps
Add a data store. Some data stores in cloud deployments, require you to first install the SecureAuth Connector.