Identikey Server Getting Started Guide - Vasco

Identikey Server 

Getting Started Guide 

3.1

Disclaimer of Warranties and Limitations of Liabilities 

Disclaimer of Warranties and Limitations of Liabilities 

The Product is provided on an 'as is' basis, without any other warranties, or conditions, express or implied, 

including but not limited to warranties of merchantable quality, merchantability of fitness for a particular purpose, 

or those arising by law, statute, usage of trade or course of dealing. The entire risk as to the results and 

performance of the product is assumed by you. Neither we nor our dealers or suppliers shall have any liability to 

you or any other person or entity for any indirect, incidental, special or consequential damages whatsoever, 

including but not limited to loss of revenue or profit, lost or damaged data of other commercial or economic loss, 

even if we have been advised of the possibility of such damages or they are foreseeable; or for claims by a third 

party. Our maximum aggregate liability to you, and that of our dealers and suppliers shall not exceed the amount 

paid by you for the Product. The limitations in this section shall apply whether or not the alleged breach or default 

is a breach of a fundamental condition or term, or a fundamental breach. Some states/countries do not allow the 

exclusion or limitation or liability for consequential or incidental damages so the above limitation may not apply to 

you. 

Copyright 

Copyright © 2009 VASCO Data Security, Inc., VASCO Data Security International GmbH. All rights reserved. 

No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any 

means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of 

VASCO Data Security Inc. 

RADIUS Documentation Disclaimer 

The RADIUS documentation featured in this manual is focused on supplying required information pertaining to the 

RADIUS server and its operation in the Identikey Server environment. It is recommended that further information be 

gathered from your NAS/RAS vendor for information on the use of RADIUS. 

Trademarks 

VASCO®, Vacman®, IDENTIKEY®, aXs GUARD, DIGIPASS®, and ® are registered or unregistered 

trademarks of VASCO Data Security, Inc. and/or VASCO Data Security International GmbH in the U.S. and other 

countries. 

Document Version: 1.1

Table of Contents 

Table of Contents 

1 Introduction.................................................................................................................................................... 4 

1.1 Identikey Server Implementation.......................................................................................................................... 4 

1.2 Identikey Server Testing...................................................................................................................................... 4 

1.3 Topics Not Included............................................................................................................................................. 4 

1.4 What You Need to Know/Have before Starting...................................................................................................... 4 

1.5 Available Guides.................................................................................................................................................. 5 

2 Install and Setup............................................................................................................................................. 6 

2.1 Basic Setup Procedure......................................................................................................................................... 6 

2.2 Install the RADIUS Client Simulator...................................................................................................................... 6 

2.3 Install Identikey Server......................................................................................................................................... 7 

2.4 Configure Identikey Server................................................................................................................................... 7 

2.5 Set Up Auditing.................................................................................................................................................. 10 

3 Testing......................................................................................................................................................... 11 

3.1 Test Local Authentication................................................................................................................................... 12 

3.2 Test Windows Back-End Authentication............................................................................................................. 14 

3.3 Test RADIUS Back-End Authentication............................................................................................................... 17 

3.4 Test Management Features............................................................................................................................... 21 

4 Demo Tokens............................................................................................................................................... 26 

4.1 Using the Demo DP300...................................................................................................................................... 26 

4.2 Using the Demo Go 1 or Go 3............................................................................................................................. 27 

5 Set up Live System....................................................................................................................................... 29 

5.1 Checklist........................................................................................................................................................... 29 

Identikey Server Getting Started Guide 3

1 Introduction 

Introduction 

This Getting Started Guide will introduce you to Identikey Server. It will help you set up a basic installation of 

Identikey Server and get to know the product and the tools it includes. It covers only basic information and the 

most common configuration requirements. Other options and more in-depth instructions are covered in other 

manuals. 

1.1 Identikey Server Implementation 

This guide covers a basic Windows implementation of Identikey Server, suitable for an evaluation or simple setup: 

Identikey Server installed with standard configuration 

Embedded PostgreSQL database as data store 

RADIUS environment 

Administration Web Interface 

It includes information on configuration of Identikey Server for specific management scenarios. 

1.2 Identikey Server Testing 

This guide will lead you through testing of management features, such as setting up auto-assignment of Digipass 

to Digipass Users. 

1.3 Topics Not Included 

This guide does not cover topics such as: 

Installation instructions 

Detailed introduction to Identikey Server, its features and components 

Detailed instructions on the use of Identikey Server 

Additional components 

Virtual Digipass 

Backup and recovery 

1.4 What You Need to Know/Have before Starting 

The encrypted DPX file provided with Digipass (unless you will only use the provided demo Digipass files) 

Transport Key for the DPX file (if using your own file) 


Installation disk or executable 

Installation Guide 

1.5 Available Guides 

The following Identikey Server guides are available: 

Product Guide 

Introduction 

The Product Guide will introduce you to the features and concepts of Identikey Server and the various options you 

have for using it. 

Getting Started Guide 

The Getting Started Guide will lead you through a standard setup and testing of key Identikey Server features. 

Windows Installation Guide 

Use this guide when planning and working through an installation of Identikey Server in a Windows environment. 

Linux Installation Guide 

Use this guide when planning and working through an installation of Identikey Server in a Linux environment. 

Administrator Reference 

In-depth information required for administration of Identikey Server. This includes references such as data attribute 

lists, backup and recovery and utility commands. 

Performance and Deployment Guide 

Contains information on common deployment models and performance statistics. 

Help Files 

Context-sensitive help accompanies the Administration Web Interface and Digipass Extension for Active Directory 

Users and Computers. 

Identikey Server SDK Programmers Guide 

In-depth information required to develop using the SDK. 


2 Install and Setup 

2.1 Basic Setup Procedure 

Install and Setup 

The diagram below illustrates the basic procedure which this Guide will take you through in the initial setup for 

Identikey Server. 

Image 1: Basic Setup Procedure 

2.2 Install the RADIUS Client Simulator 

The RADIUS Client Simulator (RCS) is a program that simulates RADIUS Authentication and Accounting processing 

in a similar fashion to RADIUS enabled Network Access Server and Firewall devices. The RCS can be used to test 

User authentication, Digipass authentication, estimate RADIUS Server performance or test system overload. 

Install the RADIUS Client Simulator on a machine in the required Domain: 

1. Locate and run radius-simulator_4_0_0.msi. 

2. Follow the prompts until the installation is complete. 

If you chose the default install location, the Simulator will be installed to the C:\Program Files\VASCO\ 

RADIUS Client Simulator directory. 

3. Launch the Simulator from the Start menu. 

Note 

The RADIUS Client Simulator uses the port 1812 for authentication requests and port 1813 for 

accounting requests, by default. 


2.3 Install Identikey Server 

Install Identikey Server according to the Basic Installation instructions in the Windows Installation Guide. 

RADIUS Topology 

When prompted to select a RADIUS topology, select either: 

Identikey Server as standalone RADIUS Server (this will require you to skip the RADIUS Back-End 

Authentication topic) 

Identikey Server in front of RADIUS Server 

SSL Certificate Password 


When prompted for a certificate password, note the password you enter. This will be used later in the Getting 

Started process. 

Automatic Settings 

Some settings which are created automatically for the Identikey Server are: 

Example Policies 

A Component record for the Identikey Server, which will point to a default Policy 

A default RADIUS Client Component record 

Auditing 

The Audit Viewer will be installed with Identikey Server. 

2.4 Configure Identikey Server 

The Administration Web Interface is the main administration tool available. It can be used to administer Digipass 

User and Digipass records, and to configure various settings and connections. See the Product Guide for more 

information. 

1. Open the Administration Web Interface. 

2. Enter your User ID and password. 

3. Click on Log in. 

2.4.1 Create a Test Policy 

To create the required Test Policy: 



2. Click on Policies -> Create. 

3. Enter the required information: 

a. Policy ID: Test 

b. Inherits from: IK3 Local Authentication 

4. Enter a description if desired. 

5. Click on Create. 

2.4.2 Set Up Client Record 

Default RADIUS Client 

Configure the default RADIUS Client record to use the Test Policy created in 2.4.1 

RADIUS Client Simulator will use this Component record. 

Note 


Create a Test Policy. 

The 

The Shared Secret for the default RADIUS Client record, and the RADIUS Client Simulator, is set 

to default. 

2.4.3 Create a Test User record 


2. Click on Users -> Create. 

3. Enter the required information. A User ID of 'Test User' may make the record easier to find. 

4. Click on Create. 

2.4.4 Import Digipass Records 

Before a Digipass may be assigned to a Digipass User, a record for it must be imported into the data store. This 

record includes all important information about the Digipass, including its serial number, Applications, and 

programming information. This information is transported to you in the form of a .dpx file. 

Demo Digipass may be used for the testing and familiarisation tasks in this guide. The .dpx file for these is located 

in \dpx. 

To import Digipass records: 


2. Click on Digipass -> Import 


3. Enter or browse for the import path and filename for the DPX file. 


4. Enter the transport key – this is 11111111111111111111111111111111 for the installed demo Digipass 

DPX files (press the 1 key 32 times). 

5. Click on Upload. 

6. Click on Next. 

7. Click on Import. 

8. Click on Finish. 

2.4.5 Assign Digipass to Test User 

Before a User can use a Digipass to login, the Digipass must be assigned to their User account within the data 

store. 

To assign a Digipass record to the Test User account: 


2. Click on Users -> Assign Digpass. 

3. Search for the Test User using the criteria on the Search User tab. 

4. Click Search. 

5. Select the Test User from the list. 

6. Click Next. 

7. Search for Digipass using the criteria on the Search Digipass tab. 

8. Select Search Now to select a specific Digipass to assign. 

9. Select Digipass from list if more than one is found. 

10. Click Next. 

11. Click Assign. 

12. Click on Finish. 

2.4.6 Configure the RADIUS Client Simulator 

Configure the RADIUS Client Simulator with the details for the Identikey Server: 

IP address 

Shared Secret (if modified from the default) 

Accounting and Authentication Port numbers (if modified from the defaults) 


2.5 Set Up Auditing 

1. Open the Audit Viewer (Start Menu -> Programs -> VASCO -> Identikey Server -> Audit Viewer). 

2. Expand the Servers item in the navigation pane. 

3. Click on Local Server. 

4. Enter the User ID and password for an administrator account in Identikey Server. 

5. Click on OK. 

A live audit connection will be established. 



3 Testing 

Testing 

This section will guide you through testing direct logins to Identikey Server and a back-end RADIUS server, testing 

Back-End Authentication, testing various management features, and the configuration or administration changes 

required. 

At various points in the process, test logins are recommended to ensure that the previous steps have not caused 

unexpected problems. This also helps in troubleshooting, as it helps to pinpoint where in the process a problem 

occurred. 

The diagram below illustrates the basic testing procedure. 

Test Pre-requisites 

If you are going to test all types of login methods and authentication options available, you will need: 

A Digipass User account with: 

A corresponding Windows User account 

A stored static password which is the same as the Windows account's password 

A Digipass or Demo Digipass with Response Only and Challenge/Response Applications, assigned to the 

Digipass User account. 

A new Policy named 'Test'. 

Modifying the Test Policy 

Each scenario will require modification of the Test Policy created in 2.4.1 

instructions to edit the Test Policy: 


2. Click on Policies -> List. 

Create a Test Policy. 

Use these 


3. Find and click on the Test Policy. 

4. Click on the required tab: 

Local Authentication and Back-End Authentication settings can be found under the Policy tab 

5. Click on Edit. 

Testing 

Dynamic User Registration, Password Autolearn and Stored Password Proxy settings can be found under 

the User tab. 

Application Type, Assignment Mode, Grace Period, Serial Number Separator and Search Upwards in Org. 

Unit Hierarchy settings can be found under the Digipass tab. 

Challenge/Response settings can be found under the Challenge tab. 

6. Make the required changes. 

7. Click on Save. 

Testing a Login via the RADIUS Client Simulator 

In each scenario, you will need to attempt a login, using the RADIUS Client Simulator. Once it is configured 

correctly, simply follow the directions below to try a login: 

1. Click on any port in the Simulated NAS Ports group to display the Manual Simulation window. 

2. Enter the User ID for the User account you are using for test logins in the User ID field. 

3. Enter the password for the User account and (if required) an OTP from the Digipass in the Password field. 

4. Click on the Login button. 

5. The Status information field will indicate the success or failure of your login. 

3.1 Test Local Authentication 

This topic covers testing logins handled by the Identikey Server, with no back-end authentication enabled. Three 

login methods will be covered: 

3.1.1 Static Password 

Static password (does not require a Digipass) 

Response Only (requires a Digipass with a Response Only application) 

Challenge/Response (requires a Digipass with a Challenge/Response application) 

Modify Test Policy 

Make these changes to the Test Policy (see Modifying the Test Policy for instructions): 

Set Local Auth. to Digipass/Password. 

Set Back-End Auth. to None. 


Set Password Autolearn to Yes. 

Check Grace Period 

Testing 

Check the record for the Digipass being used for testing. The grace period should be set for a time in the future. If 

it is not, the static password login will fail. 

Test Login 

Run a test login using the RADIUS Client Simulator (see Testing a Login via the RADIUS Client Simulator for 

instructions), using the Digipass User ID and static stored password. 

3.1.2 Response Only 



Set Application Type to Response Only. 



Test Login 


instructions), using the Digipass User ID and the OTP from your Digipass. 

3.1.3 Challenge/Response 



Set Application Type to Challenge/Response. 

Set 2-step Challenge/Response Request Method to Keyword. 

Set Keyword to 2StepCR. 



Test Login 


instructions), using the Digipass User ID and the keyword (2StepCR). Enter the Challenge provided by the RCS into 

your Digipass. Enter the same Digipass User ID and the Response provided by your Digipass. 


3.2 Test Windows Back-End Authentication 

Testing 

This topic covers testing the Identikey Server's use of Windows for back-end authentication. First, we test Identikey 

Server using only back-end authentication, then a combination of local and back-end authentication. 

Three login methods will be covered: 

Static password (does not require a Digipass) 

Response Only (requires a Digipass with a Response Only application) 

Challenge/Response (requires a Digipass with a Challenge/Response application) 

3.2.1 Back-End Authentication Only 

3.2.1.1 Static Password 



Set Local Auth. to None. 

Set Back-End Auth. to Always. 

Set Back-End Protocol to Windows. 


Check the record for the Digipass being used for testing. The grace period should be set for a time in the future. If 

it is not, the static password login will fail. 

Test Login 



3.2.2 Local and Back-End Authentication 

3.2.2.1 Static Password 







Test Login 

Testing 



3.2.2.2 Response Only 



Set Application Type to Response Only. 




Set Stored Password Proxy to Yes. 

Test Login 


instructions), using the Digipass User ID and the OTP from your Digipass. 

3.2.2.3 Challenge/Response 



Set Application Type to Challenge/Response. 

Set 2-step Challenge/Response Request Method to Keyword. 

Set Keyword to 2StepCR. 






Test Login 

Testing 


instructions), using the Digipass User ID and the keyword (2StepCR). Enter the Challenge provided by the RCS into 

your Digipass. Enter the same Digipass User ID and the Response provided by your Digipass. 


3.3 Test RADIUS Back-End Authentication 

Testing 

In this topic, you will be guided through configuring the Identikey Server to use a RADIUS Back-End Server, and 

testing Back-End Authentication using that Back-End Server. 

3.3.1 Set up Back-End RADIUS Server 

There are some steps you will need to follow in order to set up the RADIUS Server to be used for Back-End 

Authentication: 

The diagram below shows the basic process involved. For help in completing each of these steps, see the relevant 

sub-section. 

Image 2: RADIUS Server Setup 

Requirements 

To complete the recommended steps, you will need: 

An installed RADIUS Server. 


An administrator login for the RADIUS server. 

Create RADIUS Client records 

Testing 

Create a RADIUS Client record within the RADIUS Server for the machine on which the RADIUS Client Simulator will 

be running and the machine on which the Identikey Server is installed. 

Create a User account 

Create a User account in the RADIUS Server, or identify an existing account that can be used if preferred. Make 

sure this account has the necessary permissions so that a RADIUS Access-Request from both the RADIUS Client 

Simulator and from the Identikey Server will be accepted (given the correct password of course). Also make sure 

this account has some RADIUS 'reply attributes'. 

Enable Tracing 

Depending on the RADIUS Server product, some facilities will be available for tracing. This may be referred to as 

“logging” or “debugging” instead. If this is enabled, it will help to find out what is happening if the observed 

behaviour is not as expected. 

3.3.2 Test Direct Login to RADIUS Server 

Once the RADIUS Server has been set up, attempt a direct login using the RADIUS Client Simulator and the User 

account created for testing. 

1. Open the RADIUS Client Simulator. 

2. Enter the IP address of the RADIUS Server. 

3. Enter Authentication and Accounting port numbers if they vary from the default. 

4. Enter the Shared Secret you entered for the RADIUS Client created earlier. 

5. Select a protocol to use. 

6. Click on any port icon to attempt a login. 

7. Enter the User ID and password and click on Login. 

8. The 'reply attributes' set up for that User account should be displayed in the RADIUS Client Simulator. 


3.3.3 Configure Identikey Server for RADIUS Back-End Authentication 

3.3.3.1 Local and Back-End Authentication 

Testing 

Local and back-end authentication means that both the Identikey Server and the RADIUS Server will authenticate a 

login. This allows RADIUS reply attributes to be retrieved from the RADIUS Server. 

In this scenario, it is normal to use the Password Autolearn and Stored Password Proxy features. With these 

features enabled, the Identikey Server will learn the user's RADIUS Server password, so that the user does not 

need to log in with both their password and Digipass One Time Password at each login. However, the first time that 

the user logs in, they will need to provide their RADIUS Server password so that the Identikey Server can learn it. In 

subsequent logins, they can just log in with their One Time Password and the Identikey Server will send the stored 

password to the RADIUS Server. 




Set Back-End Protocol to RADIUS. 



3.3.3.2 Create Back-End Server Record 

The Identikey Server needs to be able to locate the RADIUS Server. This requires a Back-End Server record in the 

data store. To create a new Back-End Server record: 


2. Click on Back-End -> Register RADIUS Back-End. 

3. Enter a display name for the Back-End Server in the Back-End Server ID field. 

4. Enter the Authentication and Accounting IP Address and Port values. 

5. Enter the Shared Secret that was configured in the RADIUS Client record in the RADIUS Server for Identikey 

Server. 

6. Enter a suitable Timeout and No. of Retries. 

7. Click Create to create the record. 

3.3.4 Test Logins with Local and Back-End Authentication 

1. Configure the Test Policy for the login method to be tested – eg. Response-Only, Challenge/Response. 


2. Ensure that the RADIUS Client Simulator client record is using the configured Policy. 

In the RADIUS Client Simulator: 

3. Enter the IP address of the Identikey Server. 


5. Enter the User ID for the User account you are using for test logins in the User ID field. 

Testing 

6. Enter the User account's RADIUS Server password followed by an OTP from the Digipass in the Password 

field. There should be no spaces between the password and the OTP. 


8. The Status information field will indicate the success or failure of your logon. Below you should see the 

RADIUS reply attributes from the RADIUS Server. 

9. Enter a new OTP from the Digipass into the Password field, without the RADIUS Server password in front. 


11. The Status information field will indicate the success or failure of your logon. Below you should see the 

RADIUS reply attributes from the RADIUS Server. 


3.4 Test Management Features 

In this topic, you will be guided through the testing of basic management features in Identikey Server. 

3.4.1 Auto-Assignment 

Initial Setup 


2. Click on Clients -> List. 

3. Click on the client record for the RADIUS Client Simulator. 

4. Ensure that the Test Policy is selected in the Policy drop down list. 

5. Click on OK. 

6. Make these changes to the Test Policy (see Modifying the Test Policy for instructions): 



Set Back-End Protocol to RADIUS. 



Set Dynamic User Registration to No. 

Set Assignment Mode to Neither. 

Set Application Type to No Restriction. 

Set Search Upwards in Organizational Unit hierarchy to Yes. 

Set Grace Period – 7 days is the standard time period used. 

Testing 

7. Create or use a User account in the RADIUS Server which does not currently have a corresponding Digipass 

User account. 

8. Check that at least one unassigned Digipass is available in the Digipass Container. 

Test Auto-Assignment - 1 

In the following test, both Dynamic User Registration and Auto-Assignment should fail, meaning that a Digipass 

User account will not be created, and a Digipass will not be assigned to the User. This shows that the Identikey 

Server record has been configured successfully. 



10. Enter the User ID for the RADIUS Server User account you created earlier (step 7) in the User ID field. 


11. Enter the password for the RADIUS Server User account. 


The Status information field will indicate the success or failure of your logon. 

Check Test Results 

Testing 

To check whether a Digipass User account has been created for the User, search for the User account record in 

the Administration Web Interface. If it does not exist, the test has been successful. 

Modify Settings 


Set Dynamic User Registration to Yes. 

Set Assignment Mode to Auto-Assignment. 

Test Auto-Assignment - 2 

In the following test, both Dynamic User Registration and Auto-Assignment should succeed, meaning that a 

Digipass User account will be created, and an available Digipass will be assigned to the User. 




16. Enter the password for the User account. 





the Administration Web Interface. 

To check whether a Digipass has been assigned to the User: 

18. Click on Assigned Digipass. 

19. If a Digipass is listed, the User has been assigned the listed Digipass. 

20. Check the Grace Period End field to see that a Grace Period of the correct length (7 days by default) has 

been set. 


Password login 

21. Using the RADIUS Client Simulator, attempt a login using the RADIUS Server User's User ID and password 

only. If the Grace Period is still effective, this should be successful. 


OTP login 

Testing 

22. Using the RADIUS Client Simulator, attempt a login using the RADIUS Server User's User ID and One Time 

Password. This should be successful. 



only. As the OTP login from the previous step should have ended the Grace Period for the Digipass, this 

login should fail. 

24. Check the Grace Period End in the User record. It should contain today's date. 

3.4.2 Self-Assignment 

To complete this test, you will need to have a Digipass physically available, and free to be assigned to a test User 

account. 

Initial Setup 


Set Dynamic User Registration to No. 

Set Assignment Mode to Neither. 

Set Search Upwards in Organizational Unit hierarchy to Yes. 

Set Serial Number Separator to :. 

2. Create or use a User account in the RADIUS Server which does not currently have a corresponding Digipass 

User account. 

3. Check that the desired Digipass is in the Digipass Container and unassigned. 

Test Self-Assignment - 1 

In the following test, both Dynamic User Registration and Self-Assignment should fail, meaning that a Digipass 

User account will not be created, and the selected Digipass will not be assigned to the User. 




3. Enter the Serial Number for the Digipass, the Separator, the RADIUS Server User's Password, a Server PIN (if 

required) and a One Time Password from the Digipass into the Password field. eg. 98765432| 

password12340098787 (see the Login Permutations topic in the Administrator Reference for more 

information). 





A successful test should result in a failed login and no new Digipass User account created. 

Testing 



Modify Settings 


Set Dynamic User Registration to Yes. 

Set Assignment Mode to Self-Assignment. 

Test Self-Assignment - 2 

In the following test, both Dynamic User Registration and Self-Assignment should succeed, meaning that a 

Digipass User account will be created, and the intended Digipass will be assigned to the User. 




8. Enter the Serial Number for the Digipass, the Separator, the RADIUS Server User's Password, a Server PIN (if 

required) and a One Time Password from the Digipass into the Password field. eg. 98765432| 

password12340098787 (see the Login Permutations topic in the Administrator Reference for more 

information). 






To check whether the Digipass has been assigned to the User: 

10. Click on Digipass Assignment. 

11. If the Digipass is listed under this tab, it has been assigned to the Digipass User account. 


12. Check that a Grace Period has not been set. 



only. This should fail, as a Grace Period is not set for a Self-Assignment. 


OTP login 

Testing 

14. Using the RADIUS Client Simulator, attempt a login using the RADIUS Server User's User ID and One Time 

Password. This should be successful. 


4 Demo Tokens 

4.1 Using the Demo DP300 

This topic explains the activation and use of the demonstration DP300. 

4.1.1 Activate the Demo DP300 

The Demo DP300 is turned on with the < button. 

Demo Tokens 

Each time the Demo DP300 is activated it will request a 4-digit PIN number (displayed on the LCD screen). The 

PIN for Demo DP300s is initially set to 1234. 

The Demo Digipass will then prompt you to indicate the application you wish to use: 

Application 1 : Response only 

When you press 1 on the keypad, the demo DP300 will produce a 6-digit number. This response number is 

generated based on the secret code stored within the token, and the current time. 

The One Time Password displayed should be entered into the appropriate password field in the logon screen or 

web page. 

Application 2 : Digital Signature 

When you press 2 on the keypad, you will be prompted for 3 numbers (typically from an online transaction) 

comprising up to 5 digits each. When all three numbers required have been entered, a 6-digit number is generated 

(displayed on the LCD screen). This number is the digital signature for the transaction. This needs to be entered 

into the appropriate field in the digital signature web page or screen. 

Application 3: Challenge / Response 

When you press 3 on the keypad, the Digipass will present you with four dashes (- - - -) to indicate that a 

‘challenge’ must be entered. 

You may have the option of holding the optical reader to the middle of the flash sequence (the white flashing 

panels) on the logon web page if one is presented. 

Alternatively, if the challenge number is shown on the screen, you can key it in directly into the keypad. 

The demo DP300 will then calculate and display a One Time Password based on the challenge and the secret code 

stored in the DP300. The One Time Password displayed should be entered into the appropriate password field in 

the logon screen or web page. 


4.1.2 Change the PIN 

Demo Tokens 

Turn on the Demo DP300 and enter the current PIN to activate the token. Then hold down the On (

4.2.2 Obtaining a One Time Password 

Whenever the Demo Go 1/Go 3 is activated, it produces a 6-digit number on its LCD screen. 

Demo Tokens 

This response number is generated based on the secret code stored within the token, and the current time. 

At logon, the Users' Server PIN and the One Time Password from the Go 1/Go 3 should be entered as into the 

appropriate password field in the logon screen or web page. The Server PIN is initially 1234. 

For example, if the One Time Password generated by the Demo Go 1/Go 3 was 235761, 1234235761 should be 

entered in the login screen. 

4.2.3 Changing the Demo Go 1/Go 3 Server PIN 

The Demo Go 1/Go 3 Server PIN (1234) can be changed during the authentication process. 

To change the Demo Go 1/Go 3 Server PIN: 

1. Go to the login page or screen. 

2. In the user ID field, enter the User ID for the account you are using for testing. 

3. In the password field, enter the current Server PIN (1234) for the Demo Go 1/Go 3. 

4. Activate the Demo Digipass and enter the One Time Password generated in the response field directly after 

the Server PIN. 

5. Next, enter the new PIN for the Demo Go 1/Go 3 after the response in the Response field, then enter it again 

to confirm it. 

6. Submit your login to issue the new Server PIN information to the Identikey Server. 

Example 

To change the Server PIN for a Demo Digipass from 1234 to 5678, where the OTP generated was 111111, enter: 

123411111156785678 

in the password field and login. 

Any time you login using the Demo or another Go 1/Go 3, you may use this method to change your PIN, except for 

RADIUS authentications where any form of CHAP is in use (E.g., CHAP, MS-CHAP, MS-CHAP2). This is because 

the information is one-way hashed and cannot be retrieved from the packet. 

If CHAP protocols are used, refer to the User Self-Management Web Site Guide for more information about 

alternative web based methods for PIN change (eg. using your intranet). 


5 Set up Live System 

5.1 Checklist 

� Set up RADIUS Server 

Set up your RADIUS Server with the necessary User accounts and RADIUS attributes. 

� Modify RADIUS Client Configuration 

Configure the RADIUS Clients to send authentication requests to the Identikey Server. 

� Import More Digipass 

Import all required Digipass records 

Set up Live System 

� Create Digipass User Accounts 

If required, manually create Digipass User accounts. Alternatively, enable Dynamic User Registration in 

Identikey Server. 

� Create New Policy 

Create the necessary Policies in the Administration Web Interface for login authentications requested 

by the RADIUS Clients. 

� Create Component Records for the RADIUS Clients 

Create a Component record for the RADIUS Clients in the Administration Web Interface, linking them to 

the correct Policies. You may wish to use the default RADIUS Client for some or all RADIUS Clients 

instead. 

� Test Digipass Logins 

Test Digipass logins through the RADIUS Clients, using One Time Passwords.

Identikey Server Getting Started Guide - Vasco

Create successful ePaper yourself

Delete template?

Save as template?