Searching for public name or public group returns: "The following search entry was not found or returned too many matches".
Some days it works, some days it doesn't.
@Robert Berendt are you using Domino directory, Domino Ldap or Active directory?
On LDAP02 I am seeing the following in log.nsf:
05/30/2023 11:15:49 LDAP Server: Bind request for CN=Craig Strong,O=DEKKO failed: Invalid credentials specified: failed to authenticate
IDK if that's this issue with Sametime or other LDAP requests. I would have thought that "Administrator distinguished name" provided on the screen above would be the connecting factor for Sametime into ldap.
ldap02 is running Domino 12.0.2 on IBM i 7.5 on Power 9 hardware.
Sametime is ancient. Sametime 9 on Domino 9.0.1FP3 on older versions of Windows server.
@Robert Berendt
Sametime relies on the LDAP server to authenticate the user. The information that you are seeing is the response that sametime is getting from the LDAP server. if your users are able to login that means that Sametime is connecting to he LDAP server. Now as far as the error sis concerned
Follow this article:
How to obtain and read LDIF or LDAPSearch results
and
Integrating Sametime with large directories
to get additional information
Ideally the best route would be to open a case and work with support, but
Sametime 9 is no longer supported.
We keep meaning to migrate from Sametime 9 but other priorities keep coming up.
Seems like each iteration is always such a major undertaking.