Accessing Problems in Connections 4.5

Today I'm on a quest for login. I have a test environment on which login on Connections 4.5 is really random. I think the install is really good because Patrice Villemagne from Bestware basically did it, with me on his side. And he masters this installation.

Source

A. Choosing login values in Connections Wiki

Symptoms

• One user is able to login but others are not.
• Coincidentally it is the first on the list by alphabetical order, and the first created.
• Users are visible under websphere console
• Users are visible in the database (using IBM Data Studio) :

In Websphere log, an authentication error :

[05/07/13 09:27:57:664 CEST] 000000ba LTPAServerObj E   SECJ0369E: L'authentification a échoué lors de l'utilisation de LTPA. L'exception est com.ibm.websphere.wim.exception.PasswordCheckFailedException: CWWIM4529E  Echec de vérification du mot de passe pour le nom de principal 'ctest'. Cause principale : 'javax.naming.AuthenticationException: [LDAP: error code 49 - Failed, invalid credentials for CN=Charles Test,O=Org]; Resolved object: 'com.sun.jndi.ldap.LdapCtx@141d1f60''..
[05/07/13 09:27:57:680 CEST] 000000ba FormLoginExte E   SECJ0118E: Une erreur s'est produite lors de l'authentification de l'utilisateur ctest


In Domino for LDAP log, authentication error :
05/07/2013 09:27:57   LDAP Server: Bind request for CN=Charles Test,O=Org failed: Invalid credentials specified: failed to authenticate
05/07/2013 09:29:29   LDAP Server: You should full text index Domino directory names.nsf on SHOWROOM1/org to improve search performance for filters like '(&(objectclass=x)(uid=*))'

And finally I just didn't have any internet password for a few users into Domino for LDAP! :)
I was sure that I checked the box while registering them in Notes, but I guess you should never assume.
Also I full-text indexed the directory in order for search to be more effective.

Symptoms 2

Not able to login using email.

In websphere I changed LDAP Connections Properties to make sure that "mail" was included as an option to login.

This what I did instinctively, and it turns out to be wrong. This is related to Websphere login and not Connections login.

In order to set this up, use source A.

But it is already set up :

Actually I see now that some of them are able to login using mail and others are not. And those that don't work are the ones with redirection to another email. The "other email" was set but not the "internet address". The email address DID appear in websphere administration console! But they were not able to login using mail. I changed all this into Domino LDAP, launched the sync task (maybe this wasn't even necessary).

And ok now, they are able to login. The connections environment was set up correctly, but not domino.