Page History

1. In the Membership Connection Settings section, select the directory with which SecureAuth IdP will integrate for 2-Factor Authentication and assertion from the Data Store dropdown

2. Follow the distinct configuration steps for the specific data store in additional to the configuration steps on this page

• Active Directory (sAMAccountName)
• Active Directory (UPN)
• Lightweight Directory Services (AD-LDS)
• Lotus Domino
• Novell eDirectory
• Sun ONE
• Tivoli Directory
• Open LDAP
• Other LDAP
• SQL Server
• Custom – for directories not listed. This would require custom coding, so please contact SecureAuth for configuration steps / requirements
• ODBC
• ASPNETDB
• Web Service (Multi-Datastore)
• Google Apps – due to Google's recent API changes, SecureAuth IdP no longer supports Google Apps data store integration
• WebAdmin (for SecureAuth0 Admin Realm only)

No configuration is required in this section if True is selected from the Same As Above dropdown (step 3)

This section is only required for LDAP data stores

For SQL Server directories, refer to SQL User Data Store Tables and Stored Procedures Configuration Guide to create the profile mapping

For ASPNETDB directories, refer to ASPNETDB Configuration Guide to configure to data store to work with SecureAuth IdP

6. Map the SecureAuth IdP Property to the appropriate data store Field

For example, Groups is located in the memberOf data store Field

7. Change the Source from Default Provider if another directory is enabled in the Profile Connection Settings section and contains the Property

8. Check Writeable for a Property that will be changed in the data store by SecureAuth IdP

For example, user account information (telephone number) or authentication mechanisms (knowledge-based questions, fingerprints)

The Fields listed are only examples as each data store is organized differently and may have different values for each Property

Refer to LDAP Attributes / SecureAuth IdP Profile Properties Data Mappingfor more information