E0302010f: Cannot connect to authentication server: Invalid credentials.

Products

• CA Harvest Software Change Manager
• CA Harvest Software Change Manager - OpenMake Meister

Issue/Introduction

When users try to login they are getting this error:

E0302010f: Cannot connect to authentication server: Invalid credentials.

Our Harvest installation is configured to use LDAP for authentication.  What could be the problem?

Environment

Harvest Software Change Manager all versions

Cause

When troubleshooting Harvest's connection with your LDAP server there are several things to check.  If nothing has changed with Harvest and all of a sudden users cannot login, the first two questions are 

1. When did this problem start?
2. What has changed?

Below are some suggestions of thing to check in troubleshooting Harvest's connection to the LDAP server.

Resolution

• Has anything changed about the Windows computer?  Have any Windows updates or additional software been installed on the computer?
  
  
• Has anything changed about the LDAP server?  If you are using SSL or TLS to connect to the LDAP server, is it possible the certificate has expired?
  
  
• Has anything changed with the firewalls in your network?  Ports opened or closed?  Are you able to ping the LDAP server and telnet to the LDAP port from the broker machine?
  
  
• Is it possible the password has changed for the userid that Harvest uses to connect to the LDAP server?  To see which userid Harvest is using for that, look in your HServer.arg file for the "-ldapbinddn" setting.  The password for this user will either be in the HServer.arg file in plain text using the "-ldapbindpw" option or in an encrypted password dfo file specified by the "-ldapbindpwfile" option.  If the password has changed, and you need to update the encrypted password file, you can do this using the "svrenc -f" command.
  
  
• You should try using the hauthtst utility to test connectivity to the LDAP server.  If you can copy your HServer.arg to a Windows computer, attached is a Windows batch script that can read that file and create a hauthtst command based on those settings.  Then try to run this command from a command prompt on the broker machine and see if you get a successful result or the same message.

Additional Information

Here are a couple of articles that can help:

Documentation Links for Configuring LDAP Authentication in Harvest

Implementing SSL or TLS to LDAP server in Harvest