Issue with LDAP after upgrade to San Diego

[bobd1]

Anyone else having issues with LDAP after upgrading to San Diego?  We just upgraded and now LDAP doesn't work: 

When running a Test Connection on the LDAP Server the following messages are displayed

Error Messageldap://xxxxx.xxxxxxxxxx.xxx.xx:389/ Invalid credentials

Make sure this user account has login and read access to the server

Verify password

 And in LDAP Listener Status the last error details are

Exception while connecting to LDAP Server, [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090447, comment: AcceptSecurityContext error, data 52e, v3839]

The User name and password are correct as we can use them to logon to the MID Server via RDP

[bobd1 · Accepted solution]

We were able to resolve this issue. 

Our UAT instance was working fine.

This issue was only occurring in our Prod instance. We ascertained the credentials we were entering into LDAP were correct, so we rebooted both of our PROD MID Servers.
This resolved the issue and LDAP is running correctly now.  

[Gianluca Di Fil]

We experienced the same issue after patching our instance to Vancouver Patch 7.3b. The problem was caused by the following issue on the mid server 

"MID Server encryption keys do not match and are no longer valid."

Thus, the mid server was sending the wrong password to the LDAP server.  

Invalidating and re-validating the mid server solved our issue