topic Alfresco 4.0.d and Active Directory synchronization in Alfresco Archive

Alfresco 4.0.d and Active Directory synchronization

arodriguez — Fri, 21 Sep 2012 14:24:47 GMT

Hi,I've followed a lot of tutorials and book and I cannot find a way to make synchronization work.the errors that I have are :2012-09-21 11:47:43,930 INFO [web.site.EditionInterceptor] [http-bio-8080-exec-1] Successfully retrieved license information from Alfresco. 2012-09-21 11:48:35,261 INFO [

Re: Alfresco 4.0.d and Active Directory synchronization

throwback — Tue, 02 Oct 2012 13:26:24 GMT

I had a lot more success once I put the config into alfresco-global.properties in ./tomcat/shared/classes (using ubuntu 10.04 lts)

Do you need to sync with more than one ldap server? if not then put it in alfresco-global.properties.

What type ldap is this? Active Directory or another? My experience is with AD. Took me about a month to get ldap sync and kerberos SSO working but worth it in the end…

Re: Alfresco 4.0.d and Active Directory synchronization

throwback — Tue, 02 Oct 2012 13:30:03 GMT

"AuthenticationException: [LDAP: error code 49 - Invalid Credentials] Cause: The DN path or password which you have specified for the administrator is invalid."

I notice you have a space in the ldap username - no idea if this makes a difference but I always use service accounts with no spaces in, to avoid having to escape any characters (in case that is required - no idea)

Otherwise check the ad account isnt locked out, doesnt expire and that creds are correct. if necessary log in as that account on your domain somewhere. From your posted ldap-ad1 settings I would venture you are using AD.

Re: Alfresco 4.0.d and Active Directory synchronization

throwback — Tue, 02 Oct 2012 13:32:36 GMT

Oh, I know its adobe's site, but LDAP advice available here:

http://helpx.adobe.com/legacy/kb/ldap-troubleshooting.html

I also recommend you grab a copy of Softerra Ldap browser, very useful for working out search bases etc.

You may also wish to enable audit failure logging on the AD server you are auth'ing against to see if/why auth is failing from the windows events log.

Good luck!