Use this guide along with the Data Tab Configuration guide to configure a SecureAuth IdP realm that uses SQL Server as an additional Profile Provider.
1. Have an on-premises SQL Server data store
2. Designate a service account with read access (and optional write access) for SecureAuth IdP
SQL Server Configuration Steps
1. In the Profile Provider Settings section, select True from the Same as Above dropdown to copy the data store integration from the Membership Connection Settings section for use in profile connection; or select False if that directory is only used for the membership connection.
2. Select SQL Server from the Default Profile Provider dropdown if SQL is to be used as the default profile provider
If another SQL Server data store is configured in the Membership Connection Settings section, and True is selected from the Same as Above dropdown, then those settings appear in the Profile Connection Settings (below) and must be modified to reflect the settings of the new SQL Server data store
Only one SQL Server can be utilized for profile connection
If another directory is selected from the Default Profile Provider dropdown, then SQL Server must be selected from Source dropdown in the Profile Fields section for the SecureAuth IdP Properties that are mapped to SQL Server fields
Profile Connection Settings
3. Select SQL Server from the Data Store dropdown
4. Provide the Fully Qualified Domain Name (FQDN) or the IP Address in the Data Source field
5. Provide the Database Name in the Initial Catalog field
6. Select True from the Integrated Security dropdown if the IIS app pool's service account is to be used in the connection (see Integrated Auth Requirements below)
Select False to specify a SQL service account instead