Documentation

Introduction

Use this guide to configure the Admin Realm for remote access in the SecureAuth IdP Web Admin.

It is recommended that the Admin Realm be configured first to ensure the security of the appliance and the realms within it

The Admin Realm (SecureAuth0) can be accessed locally (Remote Desktop Protocol – RDP) or remotely (through web interface). If accessing it remotely, then no directory integration is required; however, it remote access is allowed, then the Data tab must be configured to allow external access. It is also recommended to configure the workflow to require 2-Factor Authentication to increase security.

Prerequisites

To enable 2-Factor Authentication to the Admin Realm (SecureAuth0), an enterprise data store is required with which SecureAuth IdP can integrate

Admin Realm Configuration Steps
Overview

 

1. In the Details section, SecureAuth0 is set as the Realm Name

2. Provide a Realm Description (optional)

Click Save once the configurations have been completed and before leaving the Overview page to avoid losing changes

Advanced Settings

 

3. Click Email Settings to configure the SMTP settings

Email Settings

 

4. Provide the Simple Mail Transfer Protocol (SMTP) Server Address through which SecureAuth IdP will send emails

5. Change the Port from the defaulted 25 if the SMTP server utilizes a different one

6. Provide the Username, Password, and/or Domain if required by the SMTP Relay

If the fields are not required by the SMTP Server, then only the Server Address and Port number must be set

7. Select True from the SSL dropdown if emails will be sent through a Secure Socket Layer (SSL)

8. Upload a Logo that will be used in the SecureAuth IdP email messages (optional)

9. Provide the Subject of the SecureAuth IdP email messages

10. Provide the Sender Address of the SecureAuth IdP email messages

11. Provide the Sender Name of the SecureAuth IdP email messages

12. Select a Template that will be used for the SecureAuth IdP email messages

Click Save once the configurations have been completed and before leaving the Email Settings page to avoid losing changes

For all Overview configuration steps, refer to Overview Tab Configuration

Data

Steps 13 - 21 are only required if allowing remote access (through web interface) to SecureAuth0 (Web Admin); and step 22 is only required if utilizing 2-Factor Authentication for remote access

13. 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

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

SecureAuth advises configuring access to the SecureAuth0 realm with security best practices in mind. Recommendations are listed below, but it is the customer's responsibility to determine the best settings for their specific deployment. These recommendations do not constitute a guarantee of security.

15. Restrict access to SecureAuth0 to a specific admin group

    1. In the corporate data store, create an admin user group comprised of only those members who will have access to the Web Admin
    2. In the User Groups (AD/LDAP) or Allowed Groups (SQL) field, enter the name of the admin group
    3. (AD/LDAP) In the User Group Check Type field, select Allow Access
    4. (AD/LDAP) Set the Groups Field field to the LDAP attribute that contains user group information, e.g. memberOf
Profile Fields

This section is for LDAP data stores only

Refer to the specific directory configuration guide for more information

 

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

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

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

18. 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

For all Data configuration steps, refer to Data Tab Configuration

Click Save once the configurations have been completed and before leaving the Data page to avoid losing changes

Workflow

 

19. In the Product Configuration section, select the Integration Method, and the Client Side Control and IE / PFX / Java Cert Type that apply to the first selection

See variations in Workflow Tab Configuration

Workflow

SecureAuth advises configuring remote access to the SecureAuth0 realm with security best practices in mind. Recommendations are listed below, but it is the customer's responsibility to determine the best settings for their specific deployment. These recommendations do not constitute a guarantee of remote security.

Enforce full authentication requirements for every logon attempt to the Admin realm (SecureAuth0)

20. Set the Public/Private Mode field to Public Mode Only

This forces users to authenticate fully on every logon attempt

21. Set Authentication Mode to Standard User / 2nd Factor / Password

For all Workflow configuration steps, refer to Workflow Tab Configuration

Click Save once the configurations have been completed and before leaving the Workflow page to avoid losing changes

Registration Methods

 

22. In the Registration Configuration section, enable at least one of the many authentication mechanisms if a 2-Factor Authentication Authentication Mode is selected in the Workflow tab

For all Registration Methods configuration steps, refer to Registration Methods Tab Configuration

Click Save once the configurations have been completed and before leaving the Registration Methods page to avoid losing changes

Post Authentication

 

23. In the Post Authentication section, the Authenticated User Redirect and Redirect To fields are auto-populated

Click Save once the configurations have been completed and before leaving the Post Authentication page to avoid losing changes

Forms Auth / SSO Token

 

24. Click View and Configure FormsAuth keys / SSO token to configure SecureAuth0's token/cookie settings (optional)

 To configure this realm's token / cookie settings, follow these steps:
Forms Authentication

 

1. If SSL is required to view the token, select True from the Require SSL dropdown

2. Choose whether SecureAuth IdP will deliver the token in a cookie to the user's browser or device:

  • UseCookies enables SecureAuth IdP to always deliver a cookie
  • UseUri disables SecureAuth IdP to deliver a cookie, and instead deliver the token in a query string
  • AutoDetect enables SecureAuth IdP to deliver a cookie if the user's settings allow it
  • UseDeviceProfile enables SecureAuth IdP to deliver a cookie if the browser's settings allow it, no matter the user's settings

3. Set the Sliding Expiration to True if the cookie remains valid as long as the user is interacting with the page

4. Set the Timeout length to determine for how many minutes a cookie is valid

No configuration is required for the Name, Login URL, or Domain fields

Machine Key

 

5. No changes are required in the Validation field, unless the default value does not match the company's requirement

If a different value is required, select it from the dropdown

6. No changes are required in the Decryption field, unless the default value does not match the company's requirement

If a different value is required, select it from the dropdown

No configuration is required for the Validation Key or Decryption Key fields

Authentication Cookies

 

7. Enable the cookie to be Persistent by selecting True - Expires after Timeout from the dropdown

Selecting False - Session Cookie enables the cookie to be valid as long as the session is open, and will expire once the browser is closed or the session expires

No configuration is required for the  Pre-Auth CookiePost-Auth Cookie, or the Clean Up Pre-Auth Cookie fields

Click Save once the configurations are completed and before leaving the Forms Auth / SSO Token page to avoid losing changes

Logs

 

25. In the Log Options section, provide the Log Instance ID, e.g. the Application Name or the realm name (SecureAuth3)

26. Check which Audit, Debug, and Error Logs to enable

 If SysLog is enabled
SysLog

 

1. Provide the FQDN or IP Address of the Syslog Server

2. Provide the SysLog Port number

 If Database is enabled
Log Database

 

1. Provide the FQDN or the IP Address of the database in the Data Source field

2. Provide the Database Name in the Initial Catalog field

3. Select True from the Integrated Security dropdown if the webpage's ID is to be included in the Connection String

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

5. Provide the User ID of the Database

6. Provide the Password associated to the User ID

7. Click Generate Connection String, and the Connection String will auto-populate based on the previous fields

8. Click Test Connection to ensure that the integration is successful

9. Click Save to all Realms if these Database settings are to be used in each SecureAuth IdP realm

For all Logs configuration steps, refer to Logs Tab Configuration

Click Save once the configurations have been completed and before leaving the Logs page to avoid losing changes