Your suggested change has been received. Thank you.


Suggest A Change….







You can enable GrIDsure authentication, so that users can enroll a GrIDsure token in a similar way as SafeNet MobilePASS+ to secure your organization’s resources without constraining users to specific devices.

During authentication, GrIDsure tokens present the user with a matrix of characters. To determine the passcode, the user enters the grid characters that correspond to their personal identification pattern (PIP). The red circles in the following image demonstrate the concept of a PIP and a resulting passcode (40DHM), assuming that user created the PIP by entering the characters in order from left to right.


Alternatively, if the user created the PIP from right to left, the passcode would be MHD04. There is no restriction on the order in which a pattern is created. In addition, cells in a pattern may be used more than once. For example, assume a left to right PIP, repeating every second cell would create a passcode of 400DHHM.

All GrIDsure authentications and errors are logged in the access logs.

Configure PIP requirements

You can configure GrIDsure requirements for the PIP, such as the type of characters that are allowed and the PIP length.

  1. On the STA Token Management console, select Policy > Token Policies > Third-Party Authentication Options.

    Token Policies

  2. In the Third-Party Token Type list, select GrIDsure and then click Edit.


  3. Select the GrIDsure options as required:

    • Allow trivial PIPs: (Not recommended) If enabled, the user can select a straight line (horizontal, vertical, diagonal), or the four corners of a square within the grid as their PIP.

    • Use numbers, Use uppercase letters, Use lowercase letters, Use special/symbolic characters: Grids display characters from the selected options. The grid size is set in the token template.

    • Minimum PIP Length: Specify the minimum number of characters for a PIP. The default is 4.

  4. Select Apply.

Configure PIN type and grid size

You set the PIN type and grid size in the token template.

  1. On the STA Token Management console, select Policy > Token Policies > Token Templates.

    Token Policies

  2. Under Token Templates, in the Type list, select GrIDsure.

    Gridsure template type

  3. Select Edit.

    Gridsure template options

  4. Select the PIN Type and Grid Size options, as required.

    For a description of the PIN type options, see token template

  5. Select Apply.

Allow users to reset their PIP

Users can reset their PIP during the authentication flow. By default, PIP reset is not allowed until you enable it.

During the PIP reset flow, the GrIDsure settings are affected:

  • The token template settings are retained. This means that the grid size and PIN requirements are unchanged. If there is a fixed PIN, the value that the user set when they first enrolled is used.

  • Server-side PIN policy settings are not saved, so the latest PIN length and complexity settings apply for non-fixed PIN scenarios.

  • Third-party authentication options are not saved, so the latest PIP length and trivial PIP settings apply.

PIP resets are recorded in the access logs. There is a log for the deletion of the existing GrIDsure, and a log for the enrollment of a new GrIDsure.

  1. On the STA Access Management console, select Settings > GrIDsure.

    Edit GrIDsure

  2. Select Edit.

    Allow PIP reset

  3. Select the toggle to Allow users to reset their personal identification pattern (PIP) within the IDP authentication flow.

  4. Select Save.

Reset your PIP

To test the PIP reset, follow the login steps as a user.

  1. Go to the login page for an application, such as the user portal, and select Start.

  2. Enter your Username and select Login.

    GrIDsure login page

  3. At the bottom of the grid page, select Other options.

    Reset grid pattern

  4. Select Reset grid pattern.

    Confirm your identity

  5. Complete the identity verification step. For example, you might need to enter a code that was emailed to you, or you might need to enter your password.

    How gridsure works

  6. On the How GrIDsure works page, select Continue.

    Set new gridsure pattern

  7. Enter your new PIP, and then select Submit.

  8. Use your new grid pattern to log in.

GrIDsure self-provisioning

To enable groups to self-provision GrIDsure tokens, see Self-provisioning rules for groups.

Self-provision with GrIDsure

To test your setup and ensure that it works as intended, you can follow the self-provisioning steps that your users will follow.

  1. Go to the login page for an application (such as the user portal), and select Start.


  2. Depending on the settings for your account, you might be prompted to enter your username and select Login.


  3. Depending on the settings for your account, you might be prompted to enter your passcode and select Login.

  4. Depending on the tokens configured for your account:

    • If you already have a token, select Add Additional Authenticator.
    • If you don't already have a token, select Add Authenticator.


  5. Depending on whether you have a synchronized password:

    • If your password is already validated, skip this step.

    • If you have a synchronized password, enter your password and select Submit.


    • If you do not have a synchronized password, STA sends you a verification code by email. Enter the code in the field provided and select Continue.


  6. Select Grid Pattern and then select Submit.



    The grid pattern option is not available if:

    An animation displays how GrIDsure works.

  7. When you are ready to enter your grid pattern, select Continue.


  8. To add the GrIDsure authenticator, enter your grid pattern and then select Submit.

    Valid grid patterns are based on the settings described in Configure PIP requirements. In addition, a grid pattern must not contain invalid characters or three or more duplicate characters (for example, 5550).


    • If the PIN type is configured as Server-side User Select, enter a PIN of your own and then select Submit. The following images show the range of PIN requirements that can be configured, from fewest (on the left) to most (on the right).

      alt_text alt_text

    • If the PIN type is Server-side Server Select or Server-side Fixed, memorize the PIN that is provided and then select Continue.


      For information about configuring PIN requirements, see PIN policy parameters.

      You are prompted to confirm that you memorized your PIN.

      • To continue, select My PIN is memorized.

      • To review your PIN, select Go back.


  9. To use the GrIDsure authenticator, enter your grid pattern and PIN (if required), and then select LOGIN.

    If configured, STA prompts you to enter a PIN before or after your grid pattern.

    The following image shows a prompt for PIN and passcode.


After successfully authenticating, the application (such as the user portal) displays.

Manage GrIDsure authenticators

To manage GrIDsure authenticators for specific users, follow the instructions in View users on the STA Access Management console.