Configuring CA Mobile OTP (OATH-Compliant) Settings
This page describes how to configure the CA Mobile OTP (OATH-Compliant) settings in CA Strong Authentication.
aatest
This page describes how to configure the CA Mobile OTP (OATH-Compliant) settings in CA Strong Authentication.
Configuring CA Mobile OTP (OATH-Compliant) Issuance Profile
A CA Mobile OTP-OATH profile can be used to specify the following attributes for CA Mobile OTPs that are complaint with OATH standards.
- Length: The length of the CA Mobile OTP
- Validity period: The period for which a CA Mobile OTP is valid.
By configuring a CA Mobile OTP-OATH profile and assigning it to one or more organizations, you can control the characteristics of CA Mobile OTP credentials that are issued their users. Use the CA Mobile OTP Profiles page to create CA Mobile OTP credential profiles.
Follow these steps:
- Click the Services and Server Configurations tab on the main menu.
- Verify that the CA Strong Authentication tab in the submenu is active.
- Under the CA Mobile OTP-OATH section, click the Issuance link to display the CA Mobile OTP-OATH Profiles page.
- Edit the fields in the Profile Configurations section, as required.
- CreateTo create a new profile:
- Select the Create option.
- Specify the Configuration Name of the new profile in the field that appears.
- UpdateTo update an existing profile, select the profile to update from the Select Configuration list that appears.
- Copy ConfigurationEnable this option if you want to create the profile by copying the configurations from an existing profile.Note:You can also copy from configurations that belong to other organizations that you have scope on.
- Available ConfigurationsSelect the profile from which the configurations are copied.
- Token TypeSelect the type of CA Mobile OTP that must be created for the user. HOTP represents counter-based tokens and TOTP represents time-based tokens.
- LengthSet the length of a CA Mobile OTP.The minimum length can be six (the default) and the maximum length can be eight characters.
- Time StepThe time interval, in seconds, during which the OTP generated by the client is the same as the OTP generated by the server. A larger time step allows the two OTPs to match for a longer period. In other words, a larger time step can accommodate a longer delay in receipt of the OTP from the client.You can enter any value from 1 to 300. The default is 30.Note:This option is applicable only for OTP-based CA Mobile OTPs.
- Logo URLEnter the URL that contains the logo to display on your client device which uses CA Mobile OTP for authenticating to CA Strong Authentication-protected applications.
- Display NameEnter the name that is used to display the CA Mobile OTP on the client device. You can either enter a fixed string or pass the following user variables as $$(<variable>)$$:
- user name (userName)
- organization name (orgName)
- credential custom attributes
- user custom attributes
- Validity Start DateSet the date from when the issued CA Mobile OTP credential is valid.The validity can start from either the date when this credential is created or you can specify a custom date.
- Validity End DateSet the date when the CA Mobile OTP expires.Use any of the following options to set the expiration date:
- Specify the duration
- Specify a custom date
- Choose Never Expires option if you want the CA Mobile OTP not to expire.
- Expand theAdvanced Configurationssection by clicking the[+]sign.
- In theCustom Attributessection, specify any extra information in theName-Valuepair format. For example, the organization information that plug-ins can use.
- In theCustom Card Attributessection, specify the additional information that you want to add to the CA Mobile OTP-OATH card. These custom attributes are available as part of the card string.
- Set the following values in theUser Validationssection:
- Select theUser Activeoption if you want to verify the user status for the following operations involving the current credential:
- Create credential
- Reissue credential
- Reset credential
- Reset validity of the credential
- Select theUser Attributeoption if you want to verify whether the user attribute matches certain values. You can set the value for the following user attributes:
- Date when the user was created
- Date when the user details were modified
- Email address
- First name
- Middle name
- Last name
- User status
- Telephone number
- Unique user identifier
User attribute check feature is availableonlyif you are performing configurations at the organization-level.
- In theMultiple Credential Optionssection, enter the description to identify the purpose for which the CA Mobile OTP is used in theUsage Typefield. For example: A user gets a temporary credential to perform a remote login to the network. The usage type for this credential can betemporary.
- ClickSaveto create or update the CA Mobile OTP profile.
- Refreshalldeployed CA Strong Authentication instances.
Configuring CA Mobile OTP (OATH-Compliant) Authentication Policy
A CA Mobile OTP-OATH policy can be used to specify the following authentication-related attributes for CA Mobile OTPs that are OATH-compliant:
- User status: The status of the user, which can be active or inactive.If the user status check is enabled, then the authentication for users in inactive state results in failure.
- Lockout criteria: The number of failed attempts after which the user credential is locked.
- Unlocking criteria:The time period after which a locked credential can be used again.
Follow these steps:
- Click the Services and Server Configurations tab on the main menu.
- Verify that the CA Strong Authentication tab in the submenu is active.
- Under the CA Mobile OTP-OATH section, click the Authentication link to display the CA Mobile OTP-OATH Authentication Policy page.
- Edit the fields in the Policy Configuration section, as required.
- CreateTo create a new policy:
- Select the Create option.
- Specify the Configuration Name of the new policy in the field that appears.
- UpdateTo update an existing policy, select the policy that you want to update from the Select Configuration list that appears.
- Copy ConfigurationEnable this option if you want to create the policy by copying the configurations from an existing policy.Note: You can also copy from configurations that belong to other organizations that you have scope on.
- Available ConfigurationsSelect the policy from which the configurations are copied.
- Authentication Look Ahead CountEnter the number of times the CA Mobile OTP counter on the CA Strong Authentication Server is increased to verify the CA Mobile OTP entered by the user. The CA Mobile OTP entered by the user is compared with all the CA Mobile OTPs that are generated from current count - Authentication Look Back Count to current count + Authentication Look Ahead Count on the server, and if the CA Mobile OTP entered by the user matches, then the user is authenticated.Note: If the client and server CA Mobile OTP matches, then that count is set as the current count on the server.
- Authentication Look Back CountEnter the number of times the CA Mobile OTP counter on the CA Strong Authentication Server is decreased to verify the CA Mobile OTP entered by the user.The CA Mobile OTP entered by the user is compared with all the CA Mobile OTPs that are generated from current count - Authentication Look Back Count to current count + Authentication Look Ahead Count on the server, and if the CA Mobile OTP entered by the user matches, then the user is authenticated.Note: If the client and server CA Mobile OTP matches, then that count is set as the current count on the server.
- Synchronization Look Ahead CountEnter the number of times the CA Mobile OTP counter on the CA Strong Authentication Server is increased to synchronize with the CA Mobile OTP counter on the client device.To synchronize the client and the server CA Mobile OTPs, the user has to provide two consecutive CA Mobile OTPs and if these CA Mobile OTPs match with the consecutive server CA Mobile OTPs in the lookup range (count - Synchronization Look Back Count to current count + Synchronization Look Ahead Count), then the server counter is synchronized with the count corresponding to the second CA Mobile OTP entered by the user.
- Synchronization Look Back CountEnter the number of times the CA Mobile OTP counter on the CA Strong Authentication Server is decreased to synchronize with the CA Mobile OTP counter on the client device.To synchronize the client and the server CA Mobile OTPs, the user has to provide two consecutive CA Mobile OTPs and if these CA Mobile OTPs match with the consecutive server CA Mobile OTPs in the lookup range (count - Synchronization Look Back Count to current count + Synchronization Look Ahead Count), then the server counter is synchronized with the count corresponding to the second CA Mobile OTP entered by the user.
- Lockout Credential AfterSpecify the number of failed attempts after which the CA Mobile OTP is locked.
- Check User Status Before AuthenticationSelect this option if you want to verify whether the user status is active, before authenticating them.
- Expand theAdvanced Configurationssection by clicking the[+]sign.
- Edit the fields in the section, as required.
- Issue WarningSpecify the number of days before the warning is sent to the calling application about the user impending credential expiration.
- Allow Successful AuthenticationSpecify the number of days for which the users can use an expired credential to log in successfully.
- Enable Automatic Credential UnlockSelect this option for the credential to be automatically unlocked after the time you specify in the following field.This field is valid only if you specify the corresponding value in the Lockout Credential After field.
- Unlock AfterSpecify the time period in seconds after which a locked credential can be used again for authentication.
- Alternate Processing OptionsTheAdvanced AuthenticationServer acts as a proxy and passes the authentication requests to other authentication servers, which are based on the following conditions:
- User Not Found: If the user trying to authenticate is not present in theAdvanced Authenticationdatabase, then the request is passed to the other server.
- Credential Not Found: If the credential with which the user is trying to authenticate is not present in theAdvanced Authenticationdatabase, then the request is passed to the other server.
- Multiple Credential Options
- Usage Type for VerificationIf you want the users to authenticate with the particular CA Mobile OTP credential, then enter the name of its usage type in this field.If you do not specify the usage type, then the default usage type CA Mobile OTP authentication policy is used.
- Click Save.
- Refreshalldeployed CA Strong Authentication Server instances.