Previous Topic: Configuring ArcotID OTP (EMV-Compliant) Issuance ProfileNext Topic: Configure Credential Management Keys


Configuring ArcotID OTP (EMV-Compliant) Authentication Policy

An ArcotID OTP-EMV policy can be used to specify the following authentication-related attributes for ArcotID OTPs that are EMV-compliant:

Follow these steps:

  1. Click the Services and Server Configurations tab on the main menu.
  2. Verify that the CA Strong Authentication tab in the submenu is active.
  3. Under the ArcotOTP-EMV section, click the Authentication link to display the ArcotOTP-EMV Authentication Policy page.
  4. Edit the fields in the Policy Configuration section, as required.
    Create

    If you choose to create a new policy, then:

    • Select the Create option.
    • Specify the Configuration Name of the new policy in the field that appears.
    Update

    If you choose to update an existing policy, then select the policy that you want to update from the Select Configuration list that appears.

    Copy Configuration

    Enable 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 Configurations

    Select the policy from which the configurations will be copied.

    Authentication Look Ahead Count

    Enter the number of times the ArcotID OTP-EMV counter on the CA AuthMinder Server is increased to verify the ArcotID OTP-EMV entered by the user. The ArcotID OTP-EMV entered by the user is compared with all the ArcotID OTPs that are generated from current count - Authentication Look Back Count to current count + Authentication Look Ahead Count on the server, and if the ArcotID OTP-EMV entered by the user matches, then the user is authenticated.

    Note: If the client and server ArcotID OTP-EMV matches, then that count is set as the current count on the server.

    Authentication Look Back Count

    Enter the number of times the ArcotID OTP-EMV counter on the CA AuthMinder Server is decreased to verify the ArcotID OTP-EMV entered by the user.

    The ArcotID OTP-EMV entered by the user is compared with all the ArcotID OTPs that are generated from current count - Authentication Look Back Count to current count + Authentication Look Ahead Count on the server, and if the ArcotID OTP-EMV entered by the user matches, then the user is authenticated.

    Note: If the client and server ArcotID OTP-EMV matches, then that count is set as the current count on the server.

    Synchronization Look Ahead Count

    Enter the number of times the ArcotID OTP-EMV counter on the CA AuthMinder Server is increased to synchronize with the ArcotID OTP-EMV counter on the client device.

    To synchronize the client and the server ArcotID OTPs, the user has to provide two consecutive ArcotID OTPs and if these ArcotID OTPs match with the consecutive server ArcotID 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 ArcotID OTP-EMV entered by the user.

    Synchronization Look Back Count

    Enter the number of times the ArcotID OTP-EMV counter on the CA AuthMinder Server is decreased to synchronize with the ArcotID OTP-EMV counter on the client device.

    To synchronize the client and the server ArcotID OTPs, the user has to provide two consecutive ArcotID OTPs and if these ArcotID OTPs match with the consecutive server ArcotID 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 ArcotID OTP-EMV entered by the user.

    Lockout Credential After

    Specify the number of failed attempts after which the ArcotID OTP-EMV will be locked.

    Check User Status Before Authentication

    Select this option if you want to verify whether the user status is active, before authenticating them.

  5. Expand the Advanced Configurations section by clicking the [+] sign.
  6. Edit the fields in the section, as required.
    Issue Warning

    Specify the number of days before the warning is sent to the calling application about the user’s impending credential expiration.

    Allow Successful Authentication

    Specify the number of days for which the users can use an expired credential to successfully log in.

    Enable Automatic Credential Unlock

    Select this option if you want 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.

    Note: The credential does not get automatically unlocked after the unlock period. The credential has to be used for successful authentication after the unlock period to get it unlocked.

    Unlock After

    Specify the number of hours after which a locked credential can be used again for authentication.

    Alternate Processing Options

    The CA AuthMinder Server acts as a proxy and passes the authentication requests to other authentication servers, based on the following conditions:

    • User Not Found: If the user trying to authenticate is not present in the CA AuthMinder database, 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 the CA AuthMinder database, then the request is passed to the other server.

    See "Configuring CA AuthMinder as RADIUS Proxy Server" for more information to enable this feature.

    Usage Type for Verification

    If you want the users to authenticate with the particular ArcotID OTP-EMV credential, then enter the name of its usage type in this field.

    If you do not specify the usage type, then the usage type mentioned in the default ArcotID OTP-EMV authentication policy is used.

  7. Click Save

    Refresh all deployed CA AuthMinder Server instances. See Refresh a Server Instance for instructions about the procedure.