Documentation

Introduction

Use this guide to configure the Overview tab in the Web Admin for each SecureAuth IdP realm.

This includes realm details, page content, and email (SMTP) settings.

Prerequisites

1. Create a New Realm for the target resource for which the configuration settings will apply

Overview Configuration Steps

 

1. Once a New Realm is created, the Realm Name will be auto-populated in the Details section (e.g. SecureAuth3)

2. Provide a Realm Description, which will appear only in the Web Admin in the left-side menu

3. Upload a Company Logo, which will appear on the login pages (optional)

If no logo is uploaded, then the SecureAuth logo will be present

4. Upload an Application Logo if this realm's target resource is an application that will be a part of a Secure Portal

This logo will appear on the Secure Portal page for Single Sign-on (SSO) access

Look and Feel

 

5. Provide the Document Title, which will appear on the browser window's tab and in the Web Admin in the left-side menu

This is typically the target resource, e.g. Google Apps

6. Provide the Page Header, which will appear at the top of the login pages

This is typically the target resource, e.g. Google Apps

The Document Title and the Page Header are typically the same

7. Choose the Theme of the login pages

The 2016 Light theme is selected by default; however, any Theme can be selected

In SecureAuth IdP version 9.2:

  • The 2012 and Legacy themes are deprecated

For appliances upgraded to version 9.2, if either the 2012 or Legacy theme was implemented prior to the upgrade, that theme will be converted to the 2016 Light theme

  • The 2016 Dark theme is not available on new appliances

For appliances upgraded to version 9.2, the 2016 Dark theme still appears as a menu option

Page Content

 

8. Select which Displayed Name will appear on the page when a user has successfully authenticated, and the Location of the Displayed Name

This is typically the Authenticated User ID

9. Provide the Forgot Username URL, the Forgot Password URL, and the Restart Login URL, which would be other SecureAuth IdP realms

If these realms are on the same domain as this new realm, then the URLs can be formatted as such: /secureauth[realm#]

Refer to SecureAuth IdP Out-of-the-box Identity Management Tools for the configuration guides

10. Choose the Location of the URLs

If no URL is provided, then the Location field can be left at default and no link will appear on the page

11. Change the Copyright Information from the default if preferred

12. Provide a URL to the EULA if desired

13. Select whether the Disclaimer is shown in the Page Footer or Not Shown on the page

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

Advanced Settings

 

14. Click Email Settings to configure the SMTP settings

 Email Settings Configuration Steps
Email Settings

 

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

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

14c. 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

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

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

14f. Provide the Subject of the SecureAuth IdP email messages

14g. Check the Show passcode in subject line box if the email will send One-time Passcodes to end-users and include the passcode in the Subject line of the message

With this feature enabled, the end-user does not need to open the message to retrieve the passcode

14h. Provide the Sender Address of the SecureAuth IdP email messages

14i. Provide the Sender Name of the SecureAuth IdP email messages

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

OTPEmailTemplate2013 is selected by default

14k. If the email will send login requests to end-users, optionally select an email template from the Login Request Email Template dropdown, or use the Default template

Click Edit to modify the selected template

Or click Add to create a new template which will be made available to any other realm

14l. If the email will send login requests to end-users, selecting Enabled from the Help Desk Info in Login Request Emails dropdown includes help desk contact information in the email footer

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

 

15. Click CSS Editor to alter the CSS code used for the login pages (optional)

 Optional Configuration Steps for CSS Editor
Theme

 

15a. Select an option from the Select CSS file to load and edit the theme dropdown

2013 is selected by default

In SecureAuth IdP version 9.2:

  • The 2012 and Legacy themes are deprecated

For appliances upgraded to version 9.2, if either the 2012 or Legacy theme was implemented prior to the upgrade, that theme will be converted to the 2016 Light theme

  • The 2016 Dark theme is not available on new appliances

For appliances upgraded to version 9.2, the 2016 Dark theme still appears as a menu option

CSS Editor

 

15b. View and edit the CSS code to make any changes to appearance of the pages

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

 

16. Click Content and Localization to define language settings and to modify the content / text that appears on the login pages (optional)

 Optional Configuration Steps for Content and Localization
For SecureAuth IdP v9.1...
Languages

 

16a. Select the Supported Languages that SecureAuth IdP will support for end-user web browsers, voice, and SMS content.

The end-user's browser settings determine which language appears. When the end-user uses SecureAuth IdP, if the browser language is set to a language enabled in a selection made here, then all SecureAuth IdP content is shown in that language. If the browser language is set to a language not supported by SecureAuth IdP, then the appliance will default to the English language.

For more information, see Multiple Language Localization Support.

16b. To configure one of the Supported Languages using the Verbiage Editor, select the language from the Select Language File dropdown.

Verbiage Editor

 

16c. The Verbiage Editor fields show text in the language that was selected in step 16b. Edit any of these fields to modify the content that appears on the appropriate page(s)

For SecureAuth IdP v9.2...
Languages

 

16a. Select the Supported Languages that SecureAuth IdP will support for end-user web browsers, voice, and SMS content

16b. Select the Default Language from the dropdown – SecureAuth IdP will use this language even if the end-user's browser is set to another language

The end-user's browser language settings determine which language appears when the end-user uses SecureAuth IdP, unless the Default Language is set to a different language

If the browser language is set to a language not supported by SecureAuth IdP, then the appliance will use the Default Language setting – note the default for this setting is English

For more information, see Multiple Language Localization Support

Verbiage Editor

 

16c. To use the Verbiage Editor to configure freeform text that appears on designated pages, select the language from the Language File to Edit dropdown

16d. The Verbiage Editor fields show text in the language that was selected in step 16c

Edit any of these fields to modify the content that appears on the appropriate page(s)

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

Related Documentation