Configuring security tokens
For users to authenticate and access resources protected with Defender, you need to configure and assign security tokens supported by Defender to them. Defender can work with a number of security tokens, which include native Defender tokens and third-party tokens.
The native Defender tokens include the following:
- Defender Soft Token Can be installed and used in various environments and operating systems, such as Android, Java Runtime Environment, iOS, and Windows.
- E-mail token Allows users to authenticate by using one-time passwords sent to their e-mail address.
- GrIDsure token Allows users to authenticate by using a GrIDsure Personal Identification Pattern (PIP).
- SMS token Allows users to authenticate by using one-time passwords sent to their SMS-capable device.
Third-party security tokens supported by Defender include Authy, DIGIPASS GO, Google Authenticator, Symantec VIP credentials, and YubiKey.
Configuring Defender Soft Token
This section provides instructions on how to configure and assign to users the following security tokens:
- Defender Soft Token for Android
- Defender Soft Token for iOS
- Defender Soft Token for Java
- Defender Soft Token for Windows
To configure and assign Defender Soft Token to a user
- On the computer where the Defender Administration Console is installed, open the Active Directory Users and Computers tool (dsa.msc).
- In the left pane (console tree), expand the appropriate nodes to select the container where the user object is located.
- In the right pane, double-click the user object, and then click the Defender tab in the dialog box that opens.
- Below the Tokens list, click the Program button.
- In the Select Token Type step, click to select the Software token option. Click Next.
- In the Select Software Token step, click to select the Defender Soft Token you want to configure and assign.
- Complete the wizard to configure and assign the Defender Soft Token.
For more information about the wizard steps and options, see Defender Token Programming Wizard reference.
Configuring GrIDsure token
Before configuring and assigning the GrIDsure token, you need to enable the use of GrIDsure for authentication in the Defender Security Policy properties. Then, you need to assign that policy to the users you want to authenticate with the GrIDsure token. For more information, see Managing Defender Security Policies.
To configure the GrIDsure token for a user
- On the computer where the Defender Administration Console is installed, open the Active Directory Users and Computers tool (dsa.msc).
- In the left pane (console tree), expand the appropriate nodes to select the container where the user object is located.
- In the right pane, double-click the user object, and then click the Defender tab in the dialog box that opens.
- Below the Tokens list, click the Program button.
- In the Select Token Type step, click to select the Software token option. Click Next.
- In the Select Software Token step, click to select the GrIDsure token option.
- Complete the wizard to configure and assign the GrIDsure token.
For more information about the wizard steps and options, see Defender Token Programming Wizard reference.
Enabling the use of Authy
You can allow users to authenticate via Defender by using one-time passwords generated with the Authy app. For more information about Authy, please visit http://www.authy.com.
To enable Authy for a user
- On the computer where the Defender Administration Console is installed, open the Active Directory Users and Computers tool (dsa.msc).
- In the left pane (console tree), expand the appropriate nodes to select the container where the user object is located.
- In the right pane, double-click the user object, and then click the Defender tab in the dialog box that opens.
- Below the Tokens list, click the Program button.
- In the Select Token Type step, click to select the Software token option. Click Next.
- In the Select Software Token step, click to select the Authy token option.
- Complete the wizard to enable Authy for the user.
For more information about the wizard steps and options, see Defender Token Programming Wizard reference.