The purpose of the section "Token Download" is to provide the system administrator to determine the token authorisation, authentication, download options and link expiry duration.

The Google Authenticator policy settings "Authorisation" and "Authentication" affect what the user must do prior to downloading a token, whist the download link expiry settings determine how long the links remain viable.

There are three options in the Authorisation policy setting;.

• • Authorisation Code not required
    When the user attempts to download the token, no authorisation code will be required. The user will be able to download the token by simply providing his/her username and password.

    When this option is selected, all tokens pushed to the user will end with the message "Your authorization code: not required" (see example below);

    
    

  • Authorisation Code required. Send Authorisation Code
    If this option is selected the link sent to the user will take the user to the deployment server, but they will then need to authenticate before they can obtain their token.

    When this option is selected, all tokens pushed to the user will end with the message "Your authorization code:", followed by the authorization code (see example below);

    
    

  • Authorisation Code required. Do not send Authorisation Code
    When the user attempts to download the token, an additional Authorisation Code will be required from the user. DualShield will not send an Authorisation Code.

    When this option is selected, all tokens pushed to the user will end with the message "Your authorization code:", followed by the authorization code (see example below);

    
    

The Authentication policy setting has two option that determine if user authentication is required when downloading the token;.

• • Authentication required
    Authentication is required when downloading the token.

    When this option is selected, all tokens pushed to the user will be sent without a quicklink component; When the link is used the user will need to supply their credentials to the deployment server before they can download the token.

    
    

  • Authentication not required
    Authentication is not required when downloading the token.

    If this option is selected the link sent to the user will take the user to the deployment server, but they will not be asked to authenticate before they can obtain their token. When the link is used the user will bypass the deployment server authentication process and will immediately be presented with the token details.