Some users have reported an issue with Active Directory which stops users from being able to login to SSL-Explorer. Upon examination of the sslexplorer.log file exceptions similar to the following are discovered:
16:04:14 ERROR ActiveDirectoryUserDatabase - Failed to get user details. javax.naming.AuthenticationException: GSSAPI [Root exception is javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Server not found in Kerberos database (7))]]
The error "Server not found in Kerberos database" indicates that the SSL-Explorer host cannot resolve the domain controller correctly. The exact cause of this problem is still unclear however it is linked to DNS resolution of the domain controller.
The Resolution
This can be resolved by adding an entry to your SSL-Explorer computer's host file. This can be found in /etc/hosts under Linux or C:/Windows/System32/Drivers/Etc under Windows. Simply add an entry which contains the correct IP address and domain controller hostname used in the AD configuration.
Example of the hosts file
# Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 sslexplorer localhost.localdomain localhost 192.168.1.8 dc.example.com