Documentation

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Introduction

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.

Prerequisites

1. Have an on-premises SQL Server data store

2. 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 False from the Same as Above dropdown

2. Select SQL Server from the Default Profile Provider dropdown if SQL Server will be used to supply the user information rather than the data store configured in the Membership Connection Settings section

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

Select False to specify a SQL service account instead

7. Select True from the Persist Security Info dropdown if access to the username and password information is allowed

8. Provide the User ID of the SecureAuth IdP Service Account (if False is selected in step 6)

9. Provide the Password associated to the User ID (if False is selected in step 6)

10. Click Generate Connection String, and the Connection String will auto-populate

11. Create a list of Allowed Groups that can access the target resource of this realm

12. Provide the Stored Procedure Name for Get Profile SP

13. Provide the Stored Procedure Name for Update Profile SP

14. Click Test Connection to ensure that the connection is successful

Refer to Data Tab Configuration to complete the configuration steps in the Data tab of the Web Admin

  • No labels