Hi Community,
Migrated from ST 11.6 to ST 12 wihtout problem, I've decided to remove everything and start from scratch (not premium). during setup inputs were:
ldap fqdn
Advanced LDAP settings
Bind DN
Bind password
But whatever I type, ST still keeps on connecting anonymously to ldap, so I've opened anonymous to ldap (only my servers can connect to ldap port....), in the custom.env the information is correct. Even tried .env, container sametime.ini etc....
Please open a case so we can assist you.
I'll do next time
Just found docker logs for community server:
Setting LDAP_HOST_ENV = myldap.company.com
Setting LDAP_PORT_ENV = 389
Setting LDAP_SSL_ENABLED_ENV = 0
Setting LDAP_SSL_PORT_ENV =
Setting LDAP_BIND_ENTRY_DN_ENV = CN=mybind,O=XXX
Setting LDAP_BIND_ENTRY_PWD_ENV = Mypassword
Setting LDAP_PERSON_RESOLVE_BASE_ENV =
Setting LDAP_GROUP_RESOLVE_BASE_ENV =
LDAP_GROUP_RESOLVE_FILTER_ENV is NOT set
LDAP_PERSON_RESOLVE_FILTER_ENV is NOT set
LDAP_HOST_ENV is NOT set
which is funny:
[notes@31ad08d77d17 Trace]$ echo $LDAP_HOST_ENV
myldap.company.coom
Anthony,
I've modified StCommunityConfig.xml (The BindDN was empty!) restarted docker , then OK.
Seen the same issue. In my case caused by faulty formatting of the LDAP_BIND_ENTRY_DN_ENV name. Using / in the DN instead of a comma, causes the issue and logs errors that can be seen with: docker-compose logs community
Attaching to sametime120_community_1
community_1 | Setting LDAP_HOST_ENV = domino01.acme.local
community_1 | Setting LDAP_PORT_ENV = 389
community_1 | Setting LDAP_SSL_ENABLED_ENV = 0
community_1 | Setting LDAP_SSL_PORT_ENV =
community_1 | Setting LDAP_BIND_ENTRY_DN_ENV = CN=SametimeLdap/O=Acme
community_1 | sed: -e expression #1, char 70: unknown option to `s'
community_1 | sed: -e expression #1, char 71: unknown option to `s'
community_1 | Setting LDAP_BIND_ENTRY_PWD_ENV = SametimeSecret
community_1 | Setting LDAP_PERSON_RESOLVE_BASE_ENV = O=Acme
community_1 | Setting LDAP_GROUP_RESOLVE_BASE_ENV =
community_1 | LDAP_GROUP_RESOLVE_FILTER_ENV is NOT set...