cancel
Showing results for 
Search instead for 
Did you mean: 

Alfresco3.2+LDAP subsystem configuration???

silverghost
Champ in-the-making
Champ in-the-making
Hello, everyone
I am new Alfrescoer, I don t know much about synchronization between alfresco and LDAP server, is there anyone who can give me a example. until now i install Alfresco  community 3.2 and Openldap, i have read about subsystem and configuration subsystem, I can´t find ldap-synchronization.propertiesand ldap-authentication.properties under tomcat/shared /classes/alfresco/extension directly. why????  could anyone tell me how i can configure LDAP subsystem correctly?

Thanks
5 REPLIES 5

gronfelt
Champ in-the-making
Champ in-the-making
The standard configuration is located under tomcat/webapps/alfresco/WEB-INF/classes/alfresco/subsystems/ (under Authentication/ldap and Synchronization/default respectively).

You could either change the files there, or if you want to make an override, replicate the subsystems directory tree into tomcat/shared/classes/alfresco/extension/ and edit the files there.

mikef
Champ in-the-making
Champ in-the-making
The configuration has changed between 3.2 and previous versions. It sounds like you have been looking at the old instructions.

The configuration is now based on Subsystems see: http://wiki.alfresco.com/wiki/Alfresco_Subsystems for a general information.
For instructions on configuring authentication see: http://wiki.alfresco.com/wiki/Alfresco_Authentication_Subsystems
For user/group synchronization see http://wiki.alfresco.com/wiki/The_Synchronization_Subsystem.

Note: You should always use overrides based on alfresco-global.properties rather than changing the default configuration

silverghost
Champ in-the-making
Champ in-the-making
Thanks, gronfelt and mikef, but i have something confused, i must configure alfresco-global.properties in which there are informations about authentication chain which could combine my ldap server. but  Must i override the ldap-authentication.properties and ldap-sychronization.properties under new folder that i have built under alfresco/extension/subsystem/Authentication and /Sychronization/default  or not? if not how can Alfresco know which LDAP server could be connected?

thank you

gronfelt
Champ in-the-making
Champ in-the-making
According to the documentation you should override the default configuration by placing properties files in tomcat/shared/classes/alfresco/extension/subsystems/Authentication and /Synchronization. To make Alfresco look there you should configure alfresco-global.properties by uncommenting the row about authentication and define your chain there (and the chain could have just one member, for instance ldap1:ldap).

At least that's how i interpret the documentation, however, I have not been able to get this working, so I think that either the documentation or the subsystems implementation is broken somehow.

The documentation says you should place your properties file in tomcat/shared/classes/alfresco/extension/subsystems/Authentication/ldap/ldap1 for instance, if you have a chain member named ldap1, but other threads in the forum indicates that the properties files needs to be placed in /Authentication/ldap rather than /Authentication/ldap/ldap1, which means that you could not have more than one chain member of a certain type (only one ldap for instance).

Sorry if this is all confusing you, but I'm pretty confused myself and I'm hoping that Mike F or anyone else might be able to sort this out.

dward
Champ on-the-rise
Champ on-the-rise
FYI it seems that the extension classpath based mechanism described here was broken in the v3.2 Community release

http://wiki.alfresco.com/wiki/Alfresco_Subsystems#Extension_classpath

See

http://forums.alfresco.com/en/viewtopic.php?f=8&t=20069#p66374

A fix for this will show up in the latest nightly builds.

And just to try to simplify things for you.

Every property of your subsystems can be set in alfresco-global.properties.

The only time you need to worry about the extension classpath mechanism described above (that isn't functioning in v3.2 Community) is when you have multiple 'instances' of the same type of subsystem. E.g. two ldap subsystems in your authentication chain.