Return
-
Title
How are Yubikeys purchased from One Identity imported? -
Description
How are Yubikeys purchased from One Identity imported?
-
Cause
The file sent from shipping are typically not be in the correct required format. The correct format is:
Device serial number, 160-bit Secret, Moving factor seed value. For example:
2507015,dd1034bb4136ab41871b859bf2fb785f0c6552c8,24016 -
Resolution
Converting the Key File
1. Change the filename extension of the .txt import file received from shipping to .csv2. Open the .csv file in Microsoft Excel. The .csv file should look similar to the following:
2507015,dd1034bb4136ab41871b859bf2fb785f0c6552c8,24016,a87280724092
2507016,d15f6bf0c0013da495b693cb6c96284a6f73a5a9,790331,a22538f57d3
The columns in the file contain the following:
A - Yubikey serial number
B - 160 bit secret seed
C - Moving factor seed value
D - Configuration password.3. Delete column D
4. Save the .csv file.
Keep the original .txt file containing the password associated with each of the Yubikeys, this will be useful if ever needing to reprogram them in the Yubikey Personalisation Tool
Importing the token objects1. On the computer where the Defender Administration Console is installed, open the Active Directory Users and Computers tool (dsa.msc).2. In the left pane (console tree), expand the appropriate domain node, and click to select the Defender container.3. On the menu bar, select Defender | Import Tokens4. Use the browse button to select the .CSV flle create previously
5. Leave the KEy field empty
4. Complete the wizard to import the token objects.