Help configuring LDAP

[ChrisAlker]

Alfresco Community v6.2.0

I am connecting a test system to my test domain controller, in the LDAP configuration properties page (https://docs.alfresco.com/5.0/concepts/auth-ldap-props.html) it has a section for group and user search bases. The advice given is 'The DN below which to run the group queries.'. My test system is configured as follows:

authentication.chain=alfinst:alfrescoNtlm,ldap1:ldap-ad

ntlm.authentication.sso.enabled=false

ldap.authentication.active=true
ldap.authentication.allowGuestLogin=false
ldap.authentication.userNameFormat=%s@chris.com
ldap.authentication.java.naming.provider.url=ldap://192.168.56.220:389
ldap.authentication.defaultAdministratorUserNames=Administrator,alfresco
ldap.synchronization.java.naming.security.principal=xxxxxxxx
ldap.synchronization.java.naming.security.credentials=xxxxxxxx
ldap.synchronization.groupSearchBase=Alfresco,OU=Groups,OU=Blackburn,DC=Chris,DC=com
ldap.synchronization.userSearchBase=Alfresco,OU=Users,OU=Blackburn,DC=Chris,DC=com

Within both users and groups I have set up 2 OUs (alfresco & nonalfresco), then I have created a test user in each group. From the advice given, one would assume that only the users below the Alfresco OUs would be able to log in, but I can log in with the users in the nonalfresco OUs too, can anyone explain why this is?

[narkuss]

To avoid auto-creation of users, we are currently using the following property:

synchronization.autoCreatePeopleOnLogin=false

We got this property by looking at default-synchronization.properties file. I think Alfresco should update the documentation about this.

I hope it solves your problem.

[ChrisAlker]

I've added that setting and it is still allowing users from the wrong OU in AD to log in. I'm using the Bitnami installer, would that make a difference? Something else worth pointing out too, is that when I navigate to:

http://127.0.0.1:81/share/page/console/admin-console/users

I get an error 'Error loading items'

[narkuss]

This error is a known bug in share 6.2.

Regarding ldap users, have you checked that these users from the wrong OU are not there from past wrong logins? The simplest way would be checking that these users can change their password from share UI. Ldap users can't change their password from share UI. 

Also, afaik, there is no bitnami installer for Alfresco 6.2... 

[ChrisAlker]

If I log in to my build and click the alfresco logo, it gives me the following detail:

Alfresco Share v6.2.0

(r7791ffba8f0b22f1ef9fa25ba17400c4657068e3-b9, Aikau 1.0.101.19, Spring Surf 6.2.0, Spring WebScripts 7.10, Freemarker 2.3.28, Rhino 1.7.11, Yui 2.9.0-alfresco-20141223)

Alfresco Community v6.2.0

(r05dbaf43-b368) schema 13001

Alfresco Community v6.2.0

(r05dbaf43-b368) schema 13001

With the latest settings, I've now found that a new user created within the 'none alfresco' user/group OUs does not get given access to the front end, so tested creating one in the alfresco OU, but wouldn't let that log in either, was hoping I had resolved the issue, as I've been banging my head against a brick wall with this trying to get a setting to work.

I just don't understand why the setting says:

ldap.synchronization.userSearchBase

The DN below which to run the user queries.

Surely if the LDAP configuration properties page states this, then it should function as outlined? Otherwise it is a bug?

Don't suppose you have any idea with regards to the 'Error loading items' issue in admin tools/users?

[narkuss]

The error loading items issue is a known share 6.2 bug as I stated in last comment.

Regarding your ldap error, I think Alfresco is not synchronizing users correctly. Check your logs, and escape the equals signs in your usersSearchBase property value adding a backslash in front of them.