Use this guide to configure the Forgot Password end-user page via the SecureAuth IdP Identity Management (IdM) Tool.
SecureAuth IdP provides configuration flexibility to allow users to reset known passwords, update forgotten passwords, unlock their own accounts, and / or unlock other users' accounts (help desk) via two methods: Enforce and Administrative.
Enforce Mode is appropriate for most Active Directory and other LDAP use cases and enforces password history requirements (i.e. does not allow passwords to be updated too frequently or to be the same as previous passwords), while Administrative Mode is more suited for SQL-type data stores that do not support / require password history checks and / or are targeted more for help desk utilization.
This guide provides configuration steps for both Enforce and Administrative modes for Forgot Password.
1. Create a New Realm for the Forgot Password Page
2. The SecureAuth IdP directory Service Account must have the write privileges to modify in order to change user passwords
3. If using Active Directory, then the following Outbound Ports must be open for password modification:
- 139 – DFSN, NetBIOS Session Service, NetLogon
- 445 – SMB / CIFS, DFSN, LSARPC, NbtSS, NetLogonR, SamR, SrvSvc
- 464 – Kerberos Change / Set Password
4. Configure the following tabs in the Web Admin before configuring the Post Authentication tab:
- Overview – the description of the realm and SMTP connections must be defined
- Data – an enterprise directory must be integrated with SecureAuth IdP
- Workflow – the way in which users will access this application must be defined
- Multi-Factor Methods – the Multi-Factor Authentication methods that will be used to access this page (if any) must be defined
5. (Optional) If using the Administrative Reset with History Check Password Reset Mode, then the 636 - SSL Outbound Port must be open for password modification
6. (Optional) Configure Google Apps to enable the Google Apps Functions, including directory password synchronization
1. In the Post Authentication section, select Password Reset from the Authenticated User Redirect dropdown
Click Save once the configurations have been completed and before leaving the Post Authentication page
2. Click Configure password reset page
Use Enforce Mode for Active Directory / LDAP directory types and if password history check is required
3. Select Enforce Password Change Requirements from the Password Reset Mode dropdown
4. Select Disabled - change own password from the Username Textbox dropdown
5. Select False from the Require Current Password dropdown
6. Select True from the Must Change Password at Next Logon dropdown
7. Select Automatically from the Unlock User Account dropdown
8. Select True from the Allow Password Change dropdown
9. Select True from the Validate Password Complexity dropdown to enforce password complexity requirements via SecureAuth IdP; or select False to not enforce additional password complexity requirements
NOTE: These requirements are in addition to the requirements configured in the directory
If the requirements set in SecureAuth IdP are more strict than the rules in the directory, then the IdP rules must be followed to successfully change a password; but if the requirements set in SecureAuth IdP are less strict than the rules in the directory, then the directory rules must be followed to successfully change a password
If the directory rules are not met, then the realm will error out and the password change will not be accepted
10. Select True from the Show Password Complexity Rules dropdown to display the configured password requirements (see the Password Complexity section below) on the Password Reset page
This setting applies only if True is selected in step 9
11. Select the SecureAuth IdP Email Profile Property that is mapped to the directory field containing the user's email address to which notifications of changed passwords are sent from the Send Email dropdown; or select Do not send to disable the email notification feature
12. Select True from the Show Exception on Page dropdown to display the reason(s) why a password change is not accepted
The error displayed is from the directory and based on the directory's password complexity requirements
Use Administrative Mode for SQL directory types and if password history check is not required / supported
3. Select Administrative Password Reset from the Password Reset Mode dropdown
4. Select Disabled - change own password from the Username Textbox dropdown
5. Select False from the Must Change Password at Next Logon dropdown
6. Select Automatically from the Unlock User Account dropdown
7. Select True from the Allow Password Change dropdown
8. Select True from the Validate Password Complexity dropdown to enforce password complexity requirements via SecureAuth IdP; or select False to not enforce additional password complexity requirements
NOTE: These requirements are in addition to the requirements configured in the directory
If the requirements set in SecureAuth IdP are more strict than the rules in the directory, then the IdP rules must be followed to successfully change a password; but if the requirements set in SecureAuth IdP are less strict than the rules in the directory, then the directory rules must be followed to successfully change a password
If the directory rules are not met, then the realm will error out and the password change will not be accepted
9. Select True from the Show Password Complexity Rules dropdown to display the configured password requirements (see the Password Complexity section below) on the Password Reset page
This setting applies only if True is selected in step 8
10. Select the SecureAuth IdP Email Profile Property that is mapped to the directory field containing the user's email address to which notifications of changed passwords are sent from the Send Email dropdown; or select Do not send to disable the email notification feature
11. Select True from the Show Exception on Page dropdown to display the reason(s) why a password change is not accepted
The error displayed is from the directory and based on the directory's password complexity requirements
(no step 12 – skip to step 13)
The Admin Mode with History Check is not supported for eDirectory.
3. Select Administrative Reset with History Check from the Password Reset Mode dropdown
4. Select Disabled - change own password from the Username Textbox dropdown
5. Select False from the Must Change Password at Next Logon dropdown
6. Select Automatically from the Unlock User Account dropdown
7. Select True from the Allow Password Change dropdown
8. Select True from the Validate Password Complexity dropdown to enforce password complexity requirements via SecureAuth IdP; or select False to not enforce additional password complexity requirements
NOTE: These requirements are in addition to the requirements configured in the directory
If the requirements set in SecureAuth IdP are more strict than the rules in the directory, then the IdP rules must be followed to successfully change a password; but if the requirements set in SecureAuth IdP are less strict than the rules in the directory, then the directory rules must be followed to successfully change a password
If the directory rules are not met, then the realm will error out and the password change will not be accepted
9. Select True from the Show Password Complexity Rules dropdown to display the configured password requirements (see the Password Complexity section below) on the Password Reset page
This setting applies only if True is selected in step 8
10. Select the SecureAuth IdP Email Profile Property that is mapped to the directory field containing the user's email address to which notifications of changed passwords are sent from the Send Email dropdown; or select Do not send to disable the email notification feature
11. Select True from the Show Exception on Page dropdown to display the reason(s) why a password change is not accepted
The error displayed is from the directory and based on the directory's password complexity requirements
(no step 12 – skip to step 13)
(OPTIONAL) 13. Configure the password complexity requirements that are enforced by SecureAuth IdP in addition to the directory's complexity requirements
These complexity requirements are enforced only if True is selected from the Validate Password Complexity dropdown
If no requirements are configured in SecureAuth IdP, then only the directory's password complexity requirements are enforced
(OPTIONAL) 14. Select True from the Using iOS Provisioning with Google Apps dropdown if directory / Google Apps password synchronization is enabled and to allow password changes to be synchronized
Refer to iOS G Suite Provision Configuration Guide for more information
Click Save once the configurations have been completed and before leaving the Password Reset page to avoid losing changes
(OPTIONAL) 15. Configure the realm for Google Apps provisioning, including password synchronization
Refer to Google Apps Provisioning for more information
Click Save once the configurations have been completed and before leaving the Post Authentication page to avoid losing changes
16. Click View and Configure Forms Auth Keys / SSO Token to configure the token / cookie settings and to configure this realm for SSO
These are optional configurations
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
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
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 Cookie, Post-Auth Cookie, or the Clean Up Pre-Auth Cookie fields
Click Save once the configurations have been completed and before leaving the Forms Auth / SSO Token page to avoid losing changes
To configure this realm for SSO, refer to SecureAuth IdP Single Sign-on Configuration
To configure this realm for Windows Desktop SSO, refer to Windows desktop SSO configuration