VACMAN Middleware Getting Started - Vasco

More documents

Recommendations

Info

VACMAN Middleware Getting Started Test Logins 3 Test Logins Using the User account to which you assigned a Digipass, and the Digipass, you can test the various authentication methods, login methods and protocols needed. You may wish to try various combinations of authentication method, login method and protocol, or simply the combination required for your system. 3.1 Test Pre-requisites If you are going to test all types of login methods available, you will need: A Digipass User account to test logins with - this can be the same one as in previous tests. A Digipass or Demo Digipass with Response Only and Challenge/Response Applications, assigned to the Digipass User account. A new Policy named 'Test'. 3.1.1 Create a Test Policy To create the required test Policy: 1. Open the Administration MMC Interface. 2. Click on the Policies node. 3. In the Policies list on the right, find and right-click VM3 Local Authentication. 4. Click on New Copy... 5. Enter Test in the Name field. 6. Enter an explanation of the Policy in the Description field. 7. Select the Inherit default settings from another Policy option button. 8. Select VM3 Local Authentication from the Inherit from Policy drop down list. 9. Click on OK. 10. If Active Directory is used as the data store, stop and start the Digipass Authentication Server service. © 2006 VASCO Data Security Inc. 14
VACMAN Middleware Getting Started Test Logins 3.2 Configure Authentication Method Create a Policy for each authentication method required, or use a 'Test' Policy which can be modified as desired. At this stage we are testing authentication without a Back-End RADIUS Server. If you wish to try out Windows Authentication, this can be done as detailed below with Windows Back- End Authentication. In this case, make sure that a corresponding active Windows user account exists. You can test the following authentication methods: Local Authentication only Windows Back-End Authentication only Local and Windows Back-End Authentication Caution – Active Directory only After changing a Policy, Component or Back-End Server record, ensure that you stop and start the Digipass Authentication Server service, to be sure that the new settings will take effect immediately. This is not necessary for an ODBC Database or Embedded Database. 3.2.1 Local Authentication Only Local authentication means that only the Authentication Server will authenticate a login. The recommended Policy settings for Local Authentication tests are: Local Auth. should be set to Digipass/Password. Back-End Auth. should be set to None. 3.2.2 Windows Back-End Authentication Only At this point, configuring the Authentication Server to use back-end authentication means that only Windows will authenticate a login. The recommended Policy settings for Back-end Authentication tests are: Local Auth. should be set to None. Back-End Auth. should be set to Always. Back-End Protocol must be set to Windows. 3.2.3 Local and Windows Back-End Authentication At this point, configuring the Authentication Server to use local and back-end authentication means that both the Authentication Server and Windows will authenticate a login. The recommended Policy settings for Local and Back-end Authentication tests are: © 2006 VASCO Data Security Inc. 15
Page 1 and 2: Modify these field values (right-cl
Page 3 and 4: VACMAN Middleware Getting Started T
Page 5 and 6: VACMAN Middleware Getting Started I
Page 13: VACMAN Middleware Getting Started I
Page 29 and 30: VACMAN Middleware Getting Started D
Page 31 and 32: VACMAN Middleware Getting Started D

VACMAN Middleware Getting Started - Vasco

Create successful ePaper yourself

Delete template?

Save as template?