How to install the WiKID Strong Authentication Server - Community Edition - Page 5

User Management

Now that you have created a Domain and a Network, client you will need to set up Users to test the system. We will manually configure a user. Of course, one of the major benefits of using WiKID is the automated initial validation system. We provide you with ASP scripts that you can run on a domain server that will allow your users to easily configure WiKID themselves.

First, click on the Users tab.

Figure 20 – The main User Management Screen

Start your WiKID software token on your PC ($ java -jar jWiKID.x.x.x.jar for example) and enter the domain code as in Figure 21 (the J2SE client is shown here).

software token

Figure 21 – Enter the Domain Code

You will be prompted to enter and verify a PIN.

software token

Figure 22 – Enter your PIN

You will receive a Registration Code back. This code is only used once during the initial validation process.

registration of software token

Fire 23 – The initial validation Registration Code

On the WiKID User Management screen, click on Manually Validate a User and you will see the registration code listed. By default a registration code can be validated anytime within 24 hours after it is created. The administrator can control this lifetime by changing the UnRegDeviceTTL value in the Parameter Settings (it is listed in minutes). Click on the registration code.

Register software token user

Figure 24 – Manually Validating a User

Once you have selected the correct Registration Code, enter the appropriate user name as shown in Figure 25.

Figure 25 - Enter the User name

Returning to the main User Management screen will show the validated user.

Figure 26 – One user is validated

 

Testing One-time passcodes on the WiKID Strong Authentication Server

Just to make sure that wAuth is working using the localhost certificate, we will edit the previously mentioned example.jsp and login with a one-time password. On the terminal of the WiKID server, edit the file with your preferred editor:

vi /opt/WiKID/tomcat/webapps/WiKIDAdmin/example.jsp

Edit line 42 and change defaultservercode to your WiKID server domain code and line 48 changing the localhost passphrase to your passphrase. Once saved, browse to https://servername/WiKIDAdmin/example.jsp. If you are not logged in, you will need to login as the WiKIDAdmin administrator. You page should look like this:

Figure 27 - The example.jsp page

Enter the username you just added to the WiKID Strong Authentication Server in the Username box under Online Login. Get a one-time password from your token client, enter it into the Passcode box and hit Check Online. If you are authenticated, you should see Success at the top of the subsequent page.

Congratulations. You have now configured the Community Version of the WiKID Strong Authentication Server. The WiKID Strong Authentication System is a dual-source two-factor authentication system. For more information on what you can do with WiKID, please visit the WiKID Website.

Share this page:

0 Comment(s)