How to make sure that after a first match in LDAP the user is matched.
I had a user logging in with shortname kbis and there is another user with shortname kbis1
The user cannot log in with kbis, he needs to log in with fullname although shortname is configured in Sametime to use as possibility.
You need to modify the authentication and resolve filter to exclude uid.
This is done in the StCommunityConfig.xml file, which lives inside the Community container.
The procedure goes like this:
- Take a copy of the existing StCommunityConfig.xml file from the Community container
- Modify the search filter and remove "uid".
- Now get the new copy of the file into the Community container and re-deploy...
This is where the procedure varies depending on if you are on Docker or K8s. We actually have some new documentation that should be published soon but I checked just now and its not there yet.
The procedure for k8s is like this topic: https://help.hcltechsw.com/sametime/1201/admin/configuring_ldap_multiple_kubernetes.html
You'll need to modify the search filter, and also include the bind credentials because you'll be overriding the default configuration with this new file. You won't need to make a copy of the entire line, you just want to modify the existing line.
If you are running on Docker to copy the file out of the community container the procedure is almost the same as this, but change the name of the file to StCommunityConfig.xml
https://help.hcltechsw.com/sametime/1201/admin/config_buscard_custom_docker.html
For example, to get the copy of the file:
docker cp <container_name>:/local/notesdata/StCommunityConfig.xml .
Perform steps 2 -4 but substitute file names.
I'll try and come back here and post links when these new help topics are available. Please open a case with support if you need assistance.
Thanks,
Casey Toole, HCL