The PIN OTP page is for end-users to receive a one-time password (OTP) to use for Multi-Factor Authentication into target resources.
1. Create a New Realm for the PIN OTP page
2. The SecureAuth IdP directory Service Account must have the write privileges in order to change/add the OTP PIN to the user account
3. 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
1. In the Multi-Factor Configuration section, under Multi-Factor Settings, select the OTP Length from the dropdown selections
This setting tells the PIN OTP page the length of the OTP to generate
Click Save once the configurations have been completed and before leaving the Multi-Factor Methods page to avoid losing changes
2. Select PIN OTP from the Authenticated User Redirect dropdown in the Post Authentication tab in the Web Admin
3. An unalterable URL will be auto-populated in the Redirect To field, which will append to the domain name and realm number in the address bar (Authorized/PINOTP.aspx)
4. A customized post authentication page can be uploaded, but it is not required
Click Save once the configurations have been completed and before leaving the Post Authentication page to avoid losing changes
4. Click View and Configure FormsAuth keys / SSO token to configure the token/cookie settings and to configure this realm for Single Sign-on (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
The following configuration steps are for realms utilizing PIN OTP as a Multi-Factor Authentication method, and not for the PIN OTP realm
1. In the Profile Fields section within the Data tab, map the PIN field to an enterprise directory field
This is where the PIN will be stored in the user's profile for future reference
Click Save once the configurations have been completed and before leaving the Data page to avoid losing changes
2. In the Multi-Factor Configuration section, select Enable from the PIN Field dropdown to enable the use of PIN OTP for Multi-Factor Authentication
3. Select False from the One Time Use dropdown to enable the use of the same PIN OTP for multiple authentication logins (only one PIN OTP from the PIN OTP page would need to be generated)
Selecting True would erase the PIN OTP after being used, and a new one will need to be generated for each authentication login (multiple PIN OTPs from the PIN OTP page would need to be generated)
No configuration is required for the Open PIN and Show When Empty fields
Click Save once the configurations have been completed and before leaving the Multi-Factor Methods page to avoid losing changes