Problème synchronisation groupe LDAP Alfresco 4

[ozim]

Bonjour,
Je vous explique mon problème :
Je dois migrer Alfresco 3.2 vers la dernière version 4.0.
J'utilise un LDAP (openLDAP) pour synchroniser mes utilisateurs et mes groupes, sauf que voilà, tout se passe bien pour la sync au niveau des users, mais au niveau des groupes, PAS MOYEN d'arriver à synchroniser mes groupes. Par moment ça me met qu'il les synchro, mais rien ne s'affiche dans Administration Console > Manage User Groups , (j'ai utilisé les mêmes paramètres dans la version 4.0 que dans la version 3.2 pour la synchro LDAP). Tout ce que j'ai, c'est les 2 groupes par défauts EMAIL_CONTRIBUTORS et ALFRESCO_ADMINISTRATORS.

Ma configuration :
Machine : Il s'agit pour le moment d'une VM sur laquelle je fais des tests en local avant de balancer tout ça en prod. 1go de ram attribué.
OS : Debian 6 64bit
Version d'Alfresco : Alfresco-4.0.c (Community)
Version de JAVA java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8.10) (6b18-1.8.10-0+squeeze2)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
Base : MySQL

 2012-02-03 09:53:15,615  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] ldap User Creation and Association: Processed 366 entries out of 366. 100 % complete. Rate: 5 per second. 0 failures detected.
 2012-02-03 09:53:15,619  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] ldap User Creation and Association: Completed batch of 366 entries
 2012-02-03 09:53:15,708  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] Finished synchronizing users and groups with user registry 'ldap'
 2012-02-03 09:53:15,709  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] 366 user(s) and 0 group(s) processed
 2012-02-03 09:53:15,709  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] Synchronizing users and groups with user registry 'ldap2'
 2012-02-03 09:53:15,718  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] Retrieving groups changed since 1 févr. 2012 12:31:15 from user registry 'ldap2'
 2012-02-03 09:53:15,727  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] ldap2 Group Analysis: Commencing batch of 0 entries
 2012-02-03 09:53:15,729  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] ldap2 Group Analysis: Completed batch of 0 entries
 2012-02-03 09:53:15,734  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] Retrieving users changed since 2 févr. 2012 23:50:34 from user registry 'ldap2'
 2012-02-03 09:53:15,856  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] ldap2 User Creation and Association: Commencing batch of 132 entries
 2012-02-03 09:53:16,052  INFO  [security.sync.ChainingUserRegistrySynchronizer] [ldap2 User Creation and Association2] ldap2 User Creation and Association: Processed 100 entries out of 132. 76 % complete. Rate: 510 per second. 0 failures detected.
 2012-02-03 09:53:16,100  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] ldap2 User Creation and Association: Processed 132 entries out of 132. 100 % complete. Rate: 540 per second. 0 failures detected.
 2012-02-03 09:53:16,109  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] ldap2 User Creation and Association: Completed batch of 132 entries
 2012-02-03 09:53:16,152  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] Finished synchronizing users and groups with user registry 'ldap2'
 2012-02-03 09:53:16,152  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] 132 user(s) and 0 group(s) processed
 2012-02-03 09:53:16,170  INFO  [management.subsystems.ChildApplicationContextFactory] [main] Startup of 'Synchronization' subsystem, ID: [Synchronization, default] complete
 2012-02-03 09:53:16,343  INFO  [service.descriptor.DescriptorService] [main] Alfresco JVM - v1.6.0_22-b04; maximum heap size 989,875MB
 2012-02-03 09:53:16,345  INFO  [service.descriptor.DescriptorService] [main] Alfresco started (Community). Current version: 4.0.0 (3979) schema 5 025. Originally installed version: 4.0.0 (3979) schema 5 025.
 2012-02-03 09:53:16,348  INFO  [management.subsystems.ChildApplicationContextFactory] [main] Starting 'ActivitiesFeed' subsystem, ID: [ActivitiesFeed, default]
 2012-02-03 09:53:16,580  INFO  [management.subsystems.ChildApplicationContextFactory] [main] Startup of 'ActivitiesFeed' subsystem, ID: [ActivitiesFeed, default] complete
 2012-02-03 09:53:16,580  INFO  [management.subsystems.ChildApplicationContextFactory] [main] Starting 'Replication' subsystem, ID: [Replication, default]
 2012-02-03 09:53:16,651  INFO  [management.subsystems.ChildApplicationContextFactory] [main] Startup of 'Replication' subsystem, ID: [Replication, default] complete
 2012-02-03 09:53:22,484  INFO  [module.vti.VtiServer] [main] Vti server started successfully on port: 7070
 2012-02-03 09:53:22,498  INFO  [module.vti.VtiServer] [main] Vti server SessionIdManagerWorkerName: jetty1
 2012-02-03 09:53:36,706  WARN  [extensions.webscripts.DeclarativeRegistry] [main] Unable to register script classpath:webscripts/org/springframework/extensions/cmis/content.get.desc.xml due to error: 01030000 Web Script document org/springframework/extensions/cmis/content.get.desc.xml is attempting to define the url '/cmis/content:GET' already defined by org/alfresco/cmis/client/content.get.desc.xml
 2012-02-03 09:53:36,707  INFO  [extensions.webscripts.DeclarativeRegistry] [main] Registered 477 Web Scripts (+1 failed), 745 URLs
 2012-02-03 09:53:36,707  INFO  [extensions.webscripts.DeclarativeRegistry] [main] Registered 2 Package Description Documents (+0 failed) 
 2012-02-03 09:53:36,707  INFO  [extensions.webscripts.DeclarativeRegistry] [main] Registered 1 Schema Description Documents (+0 failed) 
 2012-02-03 09:53:36,710  INFO  [extensions.webscripts.AbstractRuntimeContainer] [main] Initialised Repository Web Script Container (in 11059.8ms)
 2012-02-03 09:53:36,737  INFO  [extensions.webscripts.TemplateProcessorRegistry] [main] Registered template processor freemarker for extension ftl
 2012-02-03 09:53:36,738  INFO  [extensions.webscripts.ScriptProcessorRegistry] [main] Registered script processor javascript for extension js
 3 févr. 2012 09:53:48 org.apache.catalina.startup.HostConfig deployWAR
INFO: Déploiement de l'archive share.war de l'application web
2012-02-03 09:53:57,972  INFO  [extensions.webscripts.TemplateProcessorRegistry] [main] Registered template processor freemarker for extension ftl
 2012-02-03 09:53:58,185  INFO  [extensions.webscripts.ScriptProcessorRegistry] [main] Registered script processor javascript for extension js
 2012-02-03 09:53:58,186  INFO  [extensions.webscripts.TemplateProcessorRegistry] [main] Registered template processor freemarker for extension ftl
 2012-02-03 09:53:58,193  INFO  [extensions.webscripts.ScriptProcessorRegistry] [main] Registered script processor javascript for extension js
 2012-02-03 09:54:02,786  INFO  [extensions.webscripts.DeclarativeRegistry] [main] Registered 314 Web Scripts (+0 failed), 324 URLs
 2012-02-03 09:54:02,787  INFO  [extensions.webscripts.DeclarativeRegistry] [main] Registered 8 Package Description Documents (+0 failed) 
 2012-02-03 09:54:02,787  INFO  [extensions.webscripts.DeclarativeRegistry] [main] Registered 0 Schema Description Documents (+0 failed) 
 2012-02-03 09:54:03,125  INFO  [extensions.webscripts.AbstractRuntimeContainer] [main] Initialised Spring Surf Container Web Script Container (in 4911.363ms)
 2012-02-03 09:54:03,132  INFO  [extensions.webscripts.TemplateProcessorRegistry] [main] Registered template processor freemarker for extension ftl
 2012-02-03 09:54:03,138  INFO  [extensions.webscripts.ScriptProcessorRegistry] [main] Registered script processor javascript for extension js
 3 févr. 2012 09:54:03 org.apache.catalina.startup.HostConfig deployWAR
INFO: Déploiement de l'archive awe.war de l'application web
3 févr. 2012 09:54:12 org.apache.catalina.startup.HostConfig deployWAR
INFO: Déploiement de l'archive wcmqs.war de l'application web
09:54:13,463 WARN  [org.apache.myfaces.shared_impl.util.LocaleUtils] Locale name in faces-config.xml null or empty, setting locale to default locale : fr_FR
3 févr. 2012 09:54:26 org.apache.catalina.startup.HostConfig deployDirectory
INFO: Déploiement du répertoire ROOT de l'application web
3 févr. 2012 09:54:26 org.apache.coyote.http11.Http11Protocol start
INFO: Démarrage de Coyote HTTP/1.1 sur http-8080
3 févr. 2012 09:54:26 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
3 févr. 2012 09:54:26 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/87  config=null
3 févr. 2012 09:54:26 org.apache.coyote.http11.Http11Protocol start
INFO: Démarrage de Coyote HTTP/1.1 sur http-8443
3 févr. 2012 09:54:26 org.apache.catalina.startup.Catalina start
INFO: Server startup in 233201 ms
3 févr. 2012 09:54:35 org.alfresco.solr.tracker.CoreTracker trackRepository
GRAVE: First transaction was not found with the correct timestamp -> SOLR is tracking the wrong repository

‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Les lignes qui me turlupinent sont :

2012-02-03 09:53:16,152  INFO  [security.sync.ChainingUserRegistrySynchronizer] [main] 132 user(s) and 0 group(s) processed‍

et

3 févr. 2012 09:54:35 org.alfresco.solr.tracker.CoreTracker trackRepository
GRAVE: First transaction was not found with the correct timestamp -> SOLR is tracking the wrong repository‍‍

Cela fait des jours que je suis dessus, et là je vous avoue que je sèche.
Merci de votre aide.

Olivier

[rguinot]

postez éventuellement la config du subsystem LDAP que vous avez défini. Les requêtes pour les groupes (groupQuery, groupSearchBase, etc..) retournent elles les bons résultats quand vous interrogez le LDAP avec ?

J'ai également un OpenLDAP de test, pas de problème pour le synchroniser avec une 4.0

[ozim]

Bonjour,
Lorsque je fais une recherche avec ldapsearch je trouve bien les informations que je veux.

ldapsearch -x -b "ou=CsdCpd,o=sqli,c=com" -D "uid=manager,o=sqli,c=com" -h ip -p port -w password "(objectclass=sambaGroupMapping)"‍

Idem lorsque je démarre Alfresco, il m'affiche bien qu'il synchronise des groupes.

Voici mon fichier de config ldap-authentication.properties

authentication.chain=alfrescoNtlm,ldap:ldap,ldap2:ldap
# This flag enables use of this LDAP subsystem for authentication. It may be
# that this subsytem should only be used for synchronization, in which case
# this flag should be set to false.
ldap.authentication.active=true

#
# This properties file brings together the common options for LDAP authentication rather than editing the bean definitions
#
ldap.authentication.allowGuestLogin=false
# How to map the user id entered by the user to that passed through to LDAP
# - simple 
#    - this must be a DN and would be something like
#      uid=%s,ou=People,dc=company,dc=com
# - digest
#    - usually pass through what is entered
#      %s
# If not set, an LDAP query involving ldap.synchronization.personQuery and ldap.synchronization.userIdAttributeName will 
# be performed to resolve the DN dynamically. This allows directories to be structured and doesn't require the user ID to
# appear in the DN.
ldap.authentication.userNameFormat=uid\=%s,ou\=PersonSqli,o\=sqli,c\=com

# The LDAP context factory to use
ldap.authentication.java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory

# The URL to connect to the LDAP server 
ldap.authentication.java.naming.provider.url=ldap://monurlduldap:port

# The authentication mechanism to use for password validation
ldap.authentication.java.naming.security.authentication=simple

# Escape commas entered by the user at bind time
# Useful when using simple authentication and the CN is part of the DN and contains commas
ldap.authentication.escapeCommasInBind=false

# Escape commas entered by the user when setting the authenticated user
# Useful when using simple authentication and the CN is part of the DN and contains commas, and the escaped \, is 
# pulled in as part of an LDAP sync
# If this option is set to true it will break the default home folder provider as space names can not contain \
ldap.authentication.escapeCommasInUid=false

# Comma separated list of user names who should be considered administrators by default
ldap.authentication.defaultAdministratorUserNames=

# This flag enables use of this LDAP subsystem for user and group
# synchronization. It may be that this subsytem should only be used for 
# authentication, in which case this flag should be set to false.
ldap.synchronization.active=true

# The authentication mechanism to use for synchronization
ldap.synchronization.java.naming.security.authentication=simple

# The default principal to use (only used for LDAP sync)
ldap.synchronization.java.naming.security.principal=uid\=manager,o\=sqli,c\=com

# The password for the default principal (only used for LDAP sync)
ldap.synchronization.java.naming.security.credentials=password

# If positive, this property indicates that RFC 2696 paged results should be
# used to split query results into batches of the specified size. This
# overcomes any size limits imposed by the LDAP server.
ldap.synchronization.queryBatchSize=1000

# If positive, this property indicates that range retrieval should be used to fetch
# multi-valued attributes (such as member) in batches of the specified size.
# Overcomes any size limits imposed by Active Directory.        
ldap.synchronization.attributeBatchSize=1000

# The query to select all objects that represent the groups to import.
ldap.synchronization.groupQuery=(cn\=GRP_*)
#ldap.synchronization.groupQuery=,o\=sqli,c\=com

# The query to select objects that represent the groups to import that have changed since a certain time.
#ldap.synchronization.groupDifferentialQuery=(&(objectclass\=groupOfNames)(!(modifyTimestamp<\={0})))
#ldap.synchronization.groupDifferentialQuery=(objectclass\=groupOfNames)
ldap.synchronization.groupDifferentialQuery=(&(objectclass\=sambaGroupMapping)(!(modifyTimestamp<\={0})))
#ldap.synchronization.groupDifferentialQuery=(objectclass\=sambaGroupMapping)

# The query to select all objects that represent the users to import.
ldap.synchronization.personQuery=(uid\=*)

# The query to select objects that represent the users to import that have changed since a certain time.
ldap.synchronization.personDifferentialQuery=(&(objectclass\=inetOrgPerson)(!(modifyTimestamp<\={0})))
#ldap.synchronization.personDifferentialQuery=(&(objectclass\=inetOrgPerson))

# The group search base restricts the LDAP group query to a sub section of tree on the LDAP server.
ldap.synchronization.groupSearchBase=ou\=CsdCpd,o\=sqli,c\=com

# The user search base restricts the LDAP user query to a sub section of tree on the LDAP server.
ldap.synchronization.userSearchBase=ou\=PersonSqli,o\=sqli,c\=com

# The name of the operational attribute recording the last update time for a group or user.
ldap.synchronization.modifyTimestampAttributeName=modifyTimestamp

# The timestamp format. Unfortunately, this varies between directory servers.
ldap.synchronization.timestampFormat=yyyyMMddHHmmss'Z'

# The attribute name on people objects found in LDAP to use as the uid in Alfresco
ldap.synchronization.userIdAttributeName=uid

# The attribute on person objects in LDAP to map to the first name property in Alfresco
ldap.synchronization.userFirstNameAttributeName=givenName

# The attribute on person objects in LDAP to map to the last name property in Alfresco
ldap.synchronization.userLastNameAttributeName=sn

# The attribute on person objects in LDAP to map to the email property in Alfresco
ldap.synchronization.userEmailAttributeName=mail

# The attribute on person objects in LDAP to map to the organizational id  property in Alfresco
ldap.synchronization.userOrganizationalIdAttributeName=o

# The default home folder provider to use for people created via LDAP import
ldap.synchronization.defaultHomeFolderProvider=userHomesHomeFolderProvider

# The attribute on LDAP group objects to map to the authority name property in Alfresco
ldap.synchronization.groupIdAttributeName=displayName

# The attribute on LDAP group objects to map to the authority display name property in Alfresco
ldap.synchronization.groupDisplayNameAttributeName=description

# The group type in LDAP
ldap.synchronization.groupType=sambaGroupMapping

# The person type in LDAP
ldap.synchronization.personType=memberUid

# The attribute in LDAP on group objects that defines the DN for its members
ldap.synchronization.groupMemberAttributeName=memberUid

# If true progress estimation is enabled. When enabled, the user query has to be run twice in order to count entries.
ldap.synchronization.enableProgressEstimation=true

#Import Groups & Users
ldap.synchronization.import.person.cron=00 12 * * * ?
ldap.synchronization.import.group.cron=0/1 * * * * ?
ldap.synchronization.synchronizeChangesOnly=true
ldap.synchronization.syncOnStartup=true
ldap.synchronization.synchronizeChangesOnly=false‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Je ne trouve toujours pas d'où peut venir mon probleme…

[rguinot]

Votre configuration me semble farfelue.
Vous indiquez que vous utilisez OpenLDAP. avez vous modifié en profondeur le schéma ?

Vous avez par exemple :

ldap.synchronization.groupQuery=(cn\=GRP_*)
ldap.synchronization.personQuery=(uid\=*)
ldap.synchronization.groupMemberAttributeName=memberUid‍‍‍

Habituellement, pour un OpenLDAP avec schéma standard,on a plutôt, par exemple :

…
ldap.synchronization.personQuery=(objectclass\=inetOrgPerson)
ldap.synchronization.groupQuery=(objectclass\=groupOfNames)
ldap.synchronization.groupMemberAttributeName=member
…
‍‍‍‍‍‍‍

Bien entendu, il peut y avoir des variations en fonction des besoins…
Etes vous sûr de vos requêtes ? Etes vous sur de l'attribut memberUid ?

En outre, la requête que vous faites avec ldapsearch "(objectclass=sambaGroupMapping)" n'est pas la même que celle que vous avez exprimé dans la configuration puisque vous avez mis "(cn\=GRP_*)".

Laissez savoir.

[ozim]

Bonjour,
Après plus d'un mois penché sur le problème, j'ai enfin trouvé mon problème de synchro : il s'agissait juste d'ajouter la section suivante pour la synchro

synchronization.synchronizeChangesOnly=false
synchronization.syncOnStartup=true
synchronization.syncWhenMissingPeopleLogIn=true
synchronization.import.cron= 0/5 * * * * ?‍‍‍‍

et de modifier ldap.synchronization.groupDifferentialQuery

ldap.synchronization.groupDifferentialQuery=(&(objectclass\=groupOfNames)‍

Cependant un problème se pose toujours. En effet, j'ai bien mes users et mes groupes dans Alfresco, cependant, aucun user n'apparait dans mes groupes, alors qu'avec la version 3.2, j'ai bien mes users dans mes groupes.

Y a t-il une manoeuvre spéciale à effectuer ?

[ozim]

Up ?

[rguinot]

Il y a une incohérence dans votre configuration. Les requêtes différentielles sont uniquement utilisées dans une synchro différentielle. Pourquoi avoir forcé la synchro complète à chaque fois ?

Avez vous correctement renseigné groupMemberAttributeName en correspondance avec votre annuaire ?
Qu'en est il de groupQuery, personQuery, groupSearchBase, userSearchBase, …

[ozim]

Bonjour,
J'ai forcé la synchro complète à chaque fois pour qu'il essaye de me synchroniser les users dans mes groupes, car je pense qu'il faut bien que celà soit fait au moins une fois non ? Donc tant que mes users ne seront pas dans mes groupes, je garde cette conf, sauf si vous me dites que cela ne sert à rien.

Concernant ma conf ldap-authentication.properties

ldap.synchronization.groupMemberAttributeName=memberUid
ldap.synchronization.groupQuery=(cn\=GRP_*)
ldap.synchronization.personQuery=(uid\=*)
ldap.synchronization.groupSearchBase=ou\=CsdCpd,o\=enterprise,c\=com
ldap.synchronization.userSearchBase=ou\=Person,o\=enterprise,c\=com‍‍‍‍‍

Mes attributs memberUid se trouvent tous dans ces répertoires de mon ldap
ex :

cn=GRP_CONSO_meddirecteur_2, conf=GroupeUnix, ou=Aix En Provence, ou=CsdCdp, o=enterprise, c=com
cn=GRP_BuCu_supportgrcimanager_4, conf=GroupeUnix, ou=Bordeaux, ou=CsdCpd, o=enterprise, c=com
cn=GRP_BuCu_lyonlyec_26, conf=GroupUnix, ou=Lyon, ou=CsdCpd, o=enterprise, c=com‍‍‍

Je veux donc faire correspondre mes memberUid afin qu'ils soient synchro avec les groupes "cn" correspondants.

Merci de votre aide !