The purpose of the section "Token Activation" is to allow the system administrator to specify how token activation takes place, and what messages are sent when this is required.

 


Automatically activate the token when created or assigned
The token is automatically activated and usable as soon as it is created or assigned to the user.

Send Activation Code to the user when crated or assigned
The token is not activated after it is created or assigned, and not usable until it is activated by the user.

Do Nothing
The token is not activated after it is created or assigned, and not usable until it is activated by the user, and DualShield will not send an Activation Code to the user.



This setting determines if the users can request an activation code from the available portals.



This message will be sent via a message channel to the user whenever the system administrator wants the user to get in contact.

There are three options in the Token Activation policy setting;.

    • Automatically activate the token when created or assigned

      The token is automatically activated and usable as soon as it is created or assigned to the user.

      Upon creation of new tokens of this type the token ownership status is set to "ACTIVE";

    • Send Activation Code to the user when crated or assignedThe token is not activated after it is created or assigned, and not usable until it is activated by the user.

      DualShield will automatically send an Activation Code to the user via the specified Message Channel.

      Upon creation of new tokens of this type the token ownership status is set to "INACTIVE";

      Although the token is inactive, an activation link is sent to the users email account that provides an activation link;

      After clicking on the link the user is shown the token details for the currently inactive token;, and may activate the token by clicking on  the button;

      After clicking on the button the status of the token will change to "ACTIVE";

      The status change can also be confirmed on the management console;

    • Do Nothing

      The token is not activated after it is created or assigned, and not usable until it is activated by the user, and DualShield will not send an Activation Code to the user.

      When this option is set, token creation during user authentication will cause a token to be created (during authentication), the token will be created inactive, and the user will be prompted for the token activation code, and the required activation code will be sent to the user;

  • No labels