Sametime V12 MongoDB LDAP issue when using webusers  

By Remco Angioni | 1/30/23 1:57 AM | Infrastructure - Sametime | Added by Roberto Boccadoro

When you move from a Sametime version running on Domino to the Sametime V12 version, running on Docker......there could be a problem when you have webusers running in your Sametime environment. You always have to run the Sametime Name Change utility to move away from Domino (LDAP) syntax ( CN=Remco/O=ORG to CN=Remco,O=ORG) There is a problem when you have used Sametime 11.6, which already used MongoDB for chatlogging, and used WEBUSERS (and not registered users). Webusers are saved flat in MongoDB and do not contain the CN=…/O=… syntax. When you move to Sametime V12 and converted the users to LDAP and imported vpuserinfo to MongoDB, you see a loss in Contacts and Archive. Your account is no longer connected to your old chats and doesn’t contain any contacts. Why?

Sametime V12.0.1/12.0.2 cannot connect to LDAPS:636 using TLSv1.2  

By Remco Angioni | 10/31/22 4:49 AM | Infrastructure - Sametime | Added by Roberto Boccadoro

Setting up Sametime V12.0.1 and V12.0.2 BETA, I discovered that we couldn't connect to LDAPS to a Domino server, or to the AD using TLSv1.2.I discovered it in the Docker environment and noticed in the community log these lines: community_1 | stuserinfosa 2022-10-04 08:44:04.175 SEVERE 0 — 31 : createConnection : Problem Initalizing context for simple bind community_1 | javax.naming.CommunicationException: simple bind failed: stldap.domain.internal:636 [Root exception is Initial encode failure on StTlsSocket [6]]

Extra “Sametime V12 MongoDB roles” in a highly secured Mongo environment  

By Remco Angioni | 7/11/22 4:26 AM | Infrastructure - Sametime | Added by Roberto Boccadoro

When following the standard procedure for installing LDAP, MongoDB and Sametime V12. You may discover that the Sametime database user does not have enough rights. The procedure tells us that the following command for creating an user and roles should be enough: db.createUser({user: "sametimeUser", pwd: "sametime", roles:[{role:"readWrite", db:"chatlogging"},{ role:"readWrite", db:"mobileOffline"},{ role:"readWrite", db:"meeting"},{role:"dbAdmin", db:"meeting"},{role:"userAdminAnyDatabase", db:"admin"}]}) Because there was no warning or error at this point we finished the installtion and started Sametime V12, I discovered that we couldn’t login into Sametime. Even when LDAP works correctly and tells us “BIND SUCCESSFULL” in the Sametime Community log.

Sametime 11.6 IF2 installation results in a non-working proxy when you don’t have a meeting server.   

By Remco Angioni | 3/25/22 4:27 PM | Infrastructure - Sametime | Added by Oliver Busse

After installing Sametime 11.6 IF2, i discovered that the entire proxy service will not start at all. In the localhost log you can see the following warning, over and over again. After opening a support ticket, HCL discovered a problem in the code. It seems like Sametime 11.6 IF2 needs a configured meeting server in the config.