AnsweredAssumed Answered

Switched to LDAP, but user isn't recreated

Question asked by ebogaard on Jul 8, 2012
Latest reply on Jul 11, 2012 by ebogaard
Becuase of the swith from authentication-in-Alfresco to authentication-in-openldap, we now have a problem with one user. This user used to authenticate against the Alfresco-ntlm user-database, but now has to login using ldap.

Because we'd like to send out invitations via Alfresco, the authentication chain has the be alfresco-ntlm first: authentication.chain=alfrescoNtlm1:alfrescoNtlm,ldap1:ldap
This poses the following problem: after the restart, we could still login as the user with the alfresco-ntlm-password, not the openldap-password. So, probably foolishly, I deleted the user from alfresco-ntlm, in the hope it would be recreated using the ldap-connection. But now it says "The remote server may be unavailable or your authentication details have not been recognized.". So somehow Alfresco sees this user as deleted and doesn't check if it can authenticate further down the chain.

So I'm hoping you could help me with this problem. I van think of two options, but don't know how to execute those:
1. Completely delete the user from alfresco-ntlm, so that Alfresco doesn't know it is deleted and looks in ldap for the user.
2. Recreate the original user in alfresco-ntlm and migrate it to the ldap-user.
If you can think of something else, that would also be great.

By the way: this is in Alfresco 3.4d. We're not synchronizing the ldap-users with Alfresco, just authenticating. This is because we use multi tenant for some of our activities and in that situation, authentication via ldap is only possible when synchronization is disabled.

Outcomes