KB 150011
How to import users in IDENTIKEY Server 3.1 and
3.2 using a CSV file.
Creation date: 29/07/2009 Last Review: 13/09/2011 Revision number: 5
Document type: How To Security status: EXTERNAL
Summary
Users can be imported in IDENTIKEY Server 3.1 and 3.2 using a .CSV formatted file.
Depending on the datastore (ODBC or AD) this is done differently.
(For IDENTIKEY Server 3.3, see KB 150061)
Details.
• ODBC as Datastore.
In an IDENTIKEY 3.1 and 3.2 installation, using an ODBC database, the CSV user import is done using the Administration Web Interface.
Select “Import” from the drop-down list under the “USERS” tab:
In step 1, browse to the CSV file to be imported and press the “UPLOAD” button:
Applies to: IDENTIKEY Server 3.1 and 3.2
KB 150011 – 9/13/2011
© 2011 VASCO Data Security. All rights reserved.
Page 1 of 4
In step 2, you will be asked to provide the User Import Parameters.
Depending on the data in the CSV file some fields will be visible or not. In the example below the password and serial number is provided in the CSV file.
Select the desired options and press the “IMPORT” button:
• AD as Datastore.
In an IDENTIKEY 3.1 and 3.2 installation, using AD as datastore, the CSV user import is done using the TCL scripting language.
REMARK: To be able to import IDENTIKEY users in AD, the Windows AD users must already exist.
Open a DOS window (start – run – enter: cmd – OK)
Change to the bin subdirectory of the IDENTIKEY 3.1 installation directory
Enter the command “dpadmincmd.exe”
Now you will be on the TCL interpreter command line where you can start typing
TCL commands:
Enter “logon” to logon to the system (your Windows credentials will be used to logon).
Enter the command “exit” to return to the DOS prompt.
The “help” command is always available to display the available commands and
Applies to: IDENTIKEY Server 3.1 and 3.2
KB 150011 – 9/13/2011
© 2011 VASCO Data Security. All rights reserved.
Page 2 of 4
the arguments of a command. In the screenshot below, you can see the inline help for the “user import” command:
If you specify the argument “error_data” the eventual errors will be logged in the specified file (c:\err.txt in the example above).
• CSV file format.
The details on the .CSV import file are described in the Help of the webadmin.
Select the How To Import Users section:
Applies to: IDENTIKEY Server 3.1 and 3.2
KB 150011 – 9/13/2011
© 2011 VASCO Data Security. All rights reserved.
Page 3 of 4
CSV Import File format and restrictions: o
Each User account must be on a separate line in the text file. o
A header line must be included at the beginning of the file to specify the names of the fields included, and the order of the fields. o
The correct case is not required.
Note: If the database used by the IDENTIKEY Server is case-sensitive and the
IDENTIKEY Server has not been configured to convert User IDs and domain names to upper or lower case, ensure that UserIDs and domain names are in
the correct case. o
Text strings must be surrounded by double quotes.
If double quotes exist within the text string, these must be changed to double double quotes. o
These following columns/fields may exist in the text file:
UserID (maximum 255 characters)
If the data store is AD, the AD user must already exist
UserName (maximum 64 characters)
SerialNumber
This field is used to assign a specific DIGIPASS to the user.
The serial number can be formatted as written on the DIGIPASS eg.
9087653-4 or as it appears in a DIGIPASS record eg. 0090876534)
Remark: the DIGIPASS must already exist in IDENTIKEY (in the correct domain).
OrganizationalUnit (Organizational Unit must already exist in IDENTIKEY)
Domain (Domain must exist already in data store)
Password (maximum 255 characters)
Phone (maximum 64 characters)
Email (maximum 64 characters)
Mobile (maximum 64 characters)
Example CSV file (for ODBC):
Example CSV file (for AD):
Applies to: IDENTIKEY Server 3.1 and 3.2
KB 150011 – 9/13/2011
© 2011 VASCO Data Security. All rights reserved.
Page 4 of 4
