Alfresco 3.0 + OpenLDAP + CIFS: Working

[lpiguet]

After some migration pains, I was able to successfully enable Alfresco Enterprise 3.0 with users and groups coming from OpenLDAP (using clear text passwords), and a working CIFS.

I thought I would post this here. If people are interested, post a reply and I'll post more detailed steps and instructions.

Cheers,
Laurent

[dward]

In the v3.2 community release, you could easily put your own settings in alfresco-global.properties.

What you couldn't do, was override the same property sets for different subsystem instances. E.g.

authentication.chain=ldap1:ldap,ldap2:ldap

And like you say, this is now fixed in HEAD. HEAD is now being stabilized for a new community release. So make sure you report any known issues in JIRAs.

[ghilteras]

In the v3.2 community release, you could easily put your own settings in alfresco-global.properties.

no you can't. i mean, take my case:

i just try to set up a ldap chain, without doing any override, i just want to use ldap in place of ntlm okay? simplest thing to do, so I put my configuration on alfresco-global.properties file and it JUST DOESN'T WORK

i get a standard generic "redirecting to status template error: 08300004 Login failed" error. Alfresco simply ignores everything about ldap, everything I put in the global properties file, I see on the logs it loads ldap:

INFO  [org.alfresco.repo.management.subsystems.ChildApplicationContextFactory] Startup of 'Authentication' subsystem, ID: [managed, ldap1] complete

but that's it, anything related to ldap1 is ignored, the ip of the server, userid, password etc. etc. It doesnt even TRY to reach the ldap server, it just throws a clueless generic error.

but the VERY SAME configuration (the same file) works like a charm in the latest build

so what i was trying to say is why not fix the stable version? I don't want to be forced to use a latest dev version for a production env

cheers