KB 150041
What to check when you cannot log in on
IDENTIKEY Authentication Server 3.2 Web administration?
Creation date: 26/10/2010 Last Review: 10/12/2012 Revision number: 3
Document type: How To Security status: EXTERNAL
Summary
What do you need to verify when you cannot login on the IDENTIKEY Authentication
Server 3.2 web administration?
Problem details.
• Can you open the web administration login page?
⇒ No.
Check if Tomcat is running, by browsing to http://localhost:8080 .
Is the Apache Tomcat page displayed as shown in the screenshot below?
¾ No.
Tomcat is not running.
Investigate why tomcat is not running.
¾ Yes.
Tomcat is running.
Redeploy the web administration, using the IDENTIKEY Server
Configuration wizard – redeploy webadmin)
⇒ Yes.
Can you see a server in the “server :” field?
Applies to: IDENTIKEY Authentication Server 3.2
KB 150041 – 12/10/2012
© 2011 VASCO Data Security. All rights reserved.
Page 1 of 4
¾ No.
Redeploy the web administration, or add a server as explained in the
IDENTIKEY Server Administrator Reference chapter 13.
¾ Yes.
Verify that IDENTIKEY Authentication Server is listening on the SOAP port.
Browse to port 8888 of the IDENTIKEY Authentication Server.
(https://<IP-of IK server>:8888) .
If SOAP is OK, You should get a screen as shown in the screenshot below: or
In a DOS box use following command: netstat –aon|find “8888”
Verify that the PID number of the application listening to port 8888 is the ikeyserver.exe process.
Open the task manager, use view – select columns… and add the
PID column.
• If SOAP is OK.
Enable full tracing on the IDENTIKEY Authentication Server, reproduce the problem, and look in the trace file what the problem is. (1)
• SOAP is not OK.
Verify that the IDENTIKEY Authentication Server service is running.
(IDENTIKEY Authentication Server daemon for Linux installations) o
IDENTIKEY Authentication Server service is running.
Applies to: IDENTIKEY Authentication Server 3.2
KB 150041 – 12/10/2012
© 2011 VASCO Data Security. All rights reserved.
Page 2 of 4
Enable full tracing and restart the service.
Look in the trace file to see why the SOAP port is not working. (2) o
IDENTIKEY Authentication Server service is not running.
Enable full tracing and start the service.
Look in the trace file what is happening, why the service is not starting. Also check the Windows Event viewer for evidence why the
IDENTIKEY Authentication Server service is not starting.
(1) possible causes when you can not log in and IDENTIKEY Authentication Server service and SOAP are both working:
- Wrong username or Password
Æ Enter the correct credentials. (Keyboard layout? – caps lock?)
- Administrator account is missing or corrupted.
Æ Redeploy the Administration User, using the IDENTIKEY Server
Configuration wizard – rescue administrator.
- SSL certificate has changed or is expired.
Æ See KB 150013: Unable to logon to the web admin due to an incorrect SSL certificate.
- Administration client is missing or corrupted.
Æ Redeploy the Administration Client, using the IDENTIKEY Server
Configuration wizard – rescue administration client.
- If there is nothing added to the trace file while trying to open the
WebAdmin, the Firewall may be blocking the port.
Æ Stop the Firewall or add an exception to allow the SOAP Port (8888).
(Also check if you need to add an exception for the SEAL port (20003), the SEAL SSL port (20004), the radius ports…)
(2) possible problems when IDENTIKEY Authentication Server service is working and SOAP is not working:
- The SOAP port is used by an other process (binding did not succeed in the trace file).
Æ Stop the other process or use another port
- Firewall is blocking the port (no special indications in trace file).
Æ Stop the Firewall or add an exception to allow the SOAP Port (8888).
(Also check if you need to add an exception for the SEAL port (20003), the SEAL SSL port (20004), the radius ports…)
Applies to: IDENTIKEY Authentication Server 3.2
KB 150041 – 12/10/2012
© 2011 VASCO Data Security. All rights reserved.
Page 3 of 4
Schematic view:
Applies to: IDENTIKEY Authentication Server 3.2
KB 150041 – 12/10/2012
© 2011 VASCO Data Security. All rights reserved.
Page 4 of 4
