Bonjour à tous.
Je précise une chose avant tout, je suis novice et je découvre doucement Alfresco…
Alors je vais essayé detre le plus clair possible :
Alfresco est installé sur une machine tourant sous XP. Tout fonctionne correctement, j'y accède sans difficulté. J'utilise la base fourni avec l'installation, et c'est une version 2.0 d'afresco.
Je suis dans un domaine, ou il y'a un seveur tourant sous windows 2000, avec un annuaire AD.
Je souhaiterais récuperer la liste des utilisateurs dans alfresco.
Alors j'ai passé pas mal d'heure a lire les sujets de ce forum, et je sais que vous donné souvent le lien de référence vers le wiki en anglais.
J'ai essayé donc de configurer le fichier ldap-authentification-context.xml
Je l'es renomé, et je me suis aidé du fichier posté par Sam ici :
http://forum.alfresco-fr.org/viewtopic.php?pid=1701#p1701
J'ai changé l'adresse du serveur, mais je ne comprend pas très bien ce qu'il faut configurer d'autre.
Je tient juste a rapellé, que je ne connais rien en Java, et que je ne peut pas accédé au serveur AD ( je suis stagiaire….! )
Voilà donc, mon problème après modification du fichier, je relance alfresco et je n'accède carrément plus a la page pour se loguer.
Je me retrouve avec une erreur " Etat HTTP 404 - /alfresco/ ".
J'ai juste modifié le fichier ldap-authentification. Lorsque je le renome en ".sample" et que je relance le service, celà remarche.
J'espère que quelqu'un pourra prendre le temps de mexpliqué exactement la configuration de ce fichier.
Merci d'avance!
Je précise une chose avant tout, je suis novice et je découvre doucement Alfresco…
Alors je vais essayé detre le plus clair possible :
Alfresco est installé sur une machine tourant sous XP. Tout fonctionne correctement, j'y accède sans difficulté. J'utilise la base fourni avec l'installation, et c'est une version 2.0 d'afresco.
Je suis dans un domaine, ou il y'a un seveur tourant sous windows 2000, avec un annuaire AD.
Je souhaiterais récuperer la liste des utilisateurs dans alfresco.
Alors j'ai passé pas mal d'heure a lire les sujets de ce forum, et je sais que vous donné souvent le lien de référence vers le wiki en anglais.
J'ai essayé donc de configurer le fichier ldap-authentification-context.xml
Je l'es renomé, et je me suis aidé du fichier posté par Sam ici :
http://forum.alfresco-fr.org/viewtopic.php?pid=1701#p1701
J'ai changé l'adresse du serveur, mais je ne comprend pas très bien ce qu'il faut configurer d'autre.
Je tient juste a rapellé, que je ne connais rien en Java, et que je ne peut pas accédé au serveur AD ( je suis stagiaire….! )
Voilà donc, mon problème après modification du fichier, je relance alfresco et je n'accède carrément plus a la page pour se loguer.
Je me retrouve avec une erreur " Etat HTTP 404 - /alfresco/ ".
J'ai juste modifié le fichier ldap-authentification. Lorsque je le renome en ".sample" et que je relance le service, celà remarche.
J'espère que quelqu'un pourra prendre le temps de mexpliqué exactement la configuration de ce fichier.
Merci d'avance!
- N'importe qui peut se connecté a Alfresco grace a LDAP…Sa marche. Mais en tant qu'administrateur, lorsque je vais voir la liste des utilisateurs enregistré a Allfresco…Je ne vois que les utilisateurs qui se sont connecté au moins une foi ! Tout ce qui ne se sont jamais connecté, je ne l'es vois pas dans cette liste.Je te corrige : "N'importe qui peut se connecté à Alfresco grace à NTLM" et non LDAP … si l'authentification passe par NTLM
Et donc, je me suis apercu que je ne récuperer pas l'adresse email des utilisateurs. ( le champs reste vide a tous…).
Si ta liste des utilisateurs n'est pas complète, ça veut dire que la synchro LDAP ne fonctionne pas.
- Mon deuxième problème…L'authentification, j'ai testé avec IE, il maffiche la fenetre pour mettre le mot de passe ( une fenetre windows..je ne vois plus l'interface de connexion d'Alfresco..).Je ne connais pas IE, peut-être regarder du côté des sites de confiance ou des policies…
Bonjour,J'ai réglé mon problème d'auto login, il fallais ajouter l'url du serveur dans :
IE => OUTIL => Option Internet =>Sécurité =>Site de confiance
Maintenant celà fonctionne parfaitement.
Mon deuxième problème, c'est a dire la liste des utilisateurs qui n'est pas complète. Mais pourtant, n'importe qui du domaine peut se connecter sur Alfreco, et tomber sur son espace qui se crée automatiquement.
Je vous met ma configuration des fichiers:
web.xml :
<?xml version='1.0' encoding='UTF-8'?><!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"><web-app> <display-name>Alfresco Web Client</display-name> <description>Alfresco Web Client</description> <context-param> <param-name>javax.faces.STATE_SAVING_METHOD</param-name> <param-value>server</param-value> </context-param> <context-param> <param-name>javax.faces.CONFIG_FILES</param-name> <param-value>/WEB-INF/faces-config-app.xml,/WEB-INF/faces-config-beans.xml,/WEB-INF/faces-config-navigation.xml,/WEB-INF/faces-config-common.xml,/WEB-INF/faces-config-repo.xml,WEB-INF/faces-config-custom.xml,/WEB-INF/faces-config-enterprise.xml</param-value> </context-param> <context-param> <param-name>org.apache.myfaces.ALLOW_JAVASCRIPT</param-name> <param-value>true</param-value> </context-param> <context-param> <param-name>org.apache.myfaces.DETECT_JAVASCRIPT</param-name> <param-value>false</param-value> <description>This is an EXPERIMENTAL feature, so leave it off for now!</description> </context-param> <!– TODO: Change this to false for production –> <context-param> <param-name>org.apache.myfaces.PRETTY_HTML</param-name> <param-value>true</param-value> <description> If true, rendered HTML code will be formatted, so that it is "human readable". i.e. additional line separators and whitespace will be written, that do not influence the HTML code. Default: "true" </description> </context-param> <context-param> <param-name>org.apache.myfaces.AUTO_SCROLL</param-name> <param-value>false</param-value> <description> If true, a javascript function will be rendered that is able to restore the former vertical scroll on every request. Convenient feature if you have pages with long lists and you do not want the browser page to always jump to the top if you trigger a link or button action that stays on the same page. Default: "false" </description> </context-param> <context-param> <param-name>contextConfigLocation</param-name> <param-value> classpath:alfresco/web-client-application-context.xml classpath:web-services-application-context.xml classpath:alfresco/application-context.xml </param-value> <description>Spring config file locations</description> </context-param> <filter> <filter-name>Authentication Filter</filter-name> <filter-class>org.alfresco.web.app.servlet.NTLMAuthenticationFilter</filter-class> </filter> <filter-mapping> <filter-name>Authentication Filter</filter-name> <url-pattern>/navigate/*</url-pattern> </filter-mapping> <filter> <filter-name>WebDAV Authentication Filter</filter-name> <filter-class>org.alfresco.repo.webdav.auth.NTLMAuthenticationFilter</filter-class> </filter> <filter> <filter-name>Admin Authentication Filter</filter-name> <filter-class>org.alfresco.web.app.servlet.AdminAuthenticationFilter</filter-class> </filter> <filter-mapping> <filter-name>Authentication Filter</filter-name> <url-pattern>/faces/*</url-pattern> </filter-mapping> <!– For NTLM authentication support enable the following mapping –> <!– (Enterprise version only) –> <!– <filter-mapping> <filter-name>Authentication Filter</filter-name> <url-pattern>/navigate/*</url-pattern> </filter-mapping> –> <filter-mapping> <filter-name>WebDAV Authentication Filter</filter-name> <url-pattern>/webdav/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>Admin Authentication Filter</filter-name> <url-pattern>/faces/jsp/admin/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>Admin Authentication Filter</filter-name> <url-pattern>/faces/jsp/categories/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>Admin Authentication Filter</filter-name> <url-pattern>/faces/jsp/groups/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>Admin Authentication Filter</filter-name> <url-pattern>/faces/jsp/users/delete-user.jsp</url-pattern> </filter-mapping> <filter-mapping> <filter-name>Admin Authentication Filter</filter-name> <url-pattern>/faces/jsp/users/users.jsp</url-pattern> </filter-mapping> <filter-mapping> <filter-name>Admin Authentication Filter</filter-name> <url-pattern>/faces/jsp/dialog/system-info.jsp</url-pattern> </filter-mapping> <listener> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class> </listener> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> <listener> <listener-class>org.alfresco.web.app.ContextListener</listener-class> </listener> <!– Faces Servlet –> <servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet> <servlet-name>uploadFile</servlet-name> <servlet-class>org.alfresco.web.app.servlet.UploadFileServlet</servlet-class> </servlet> <servlet> <servlet-name>downloadContent</servlet-name> <servlet-class>org.alfresco.web.app.servlet.DownloadContentServlet</servlet-class> </servlet> <servlet> <servlet-name>guestDownloadContent</servlet-name> <servlet-class>org.alfresco.web.app.servlet.GuestDownloadContentServlet</servlet-class> </servlet> <servlet> <servlet-name>guestTemplateContent</servlet-name> <servlet-class>org.alfresco.web.app.servlet.GuestTemplateContentServlet</servlet-class> </servlet> <servlet> <servlet-name>externalAccess</servlet-name> <servlet-class>org.alfresco.web.app.servlet.ExternalAccessServlet</servlet-class> </servlet> <servlet> <servlet-name>templateContent</servlet-name> <servlet-class>org.alfresco.web.app.servlet.TemplateContentServlet</servlet-class> </servlet> <servlet> <servlet-name>commandServlet</servlet-name> <servlet-class>org.alfresco.web.app.servlet.CommandServlet</servlet-class> </servlet> <servlet> <servlet-name>ajaxServlet</servlet-name> <servlet-class>org.alfresco.web.app.servlet.ajax.AjaxServlet</servlet-class> </servlet> <servlet> <servlet-name>axis</servlet-name> <servlet-class>org.apache.axis.transport.http.AxisServlet</servlet-class> <load-on-startup>5</load-on-startup> </servlet> <servlet> <servlet-name>WebDAV</servlet-name> <servlet-class>org.alfresco.repo.webdav.WebDAVServlet</servlet-class> <init-param> <param-name>store</param-name> <param-value>workspace://SpacesStore</param-value> </init-param> <init-param> <param-name>rootPath</param-name> <param-value>/app:company_home</param-value> </init-param> <load-on-startup>5</load-on-startup> </servlet> <servlet> <servlet-name>JBPMDeployProcessServlet</servlet-name> <servlet-class>org.alfresco.web.app.servlet.JBPMDeployProcessServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>/faces/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>uploadFile</servlet-name> <url-pattern>/uploadFileServlet</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>downloadContent</servlet-name> <url-pattern>/download/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>guestDownloadContent</servlet-name> <url-pattern>/guestDownload/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>guestTemplateContent</servlet-name> <url-pattern>/guestTemplate/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>externalAccess</servlet-name> <url-pattern>/navigate/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>templateContent</servlet-name> <url-pattern>/template/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>commandServlet</servlet-name> <url-pattern>/command/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>ajaxServlet</servlet-name> <url-pattern>/ajax/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>axis</servlet-name> <url-pattern>/api/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>WebDAV</servlet-name> <url-pattern>/webdav/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>JBPMDeployProcessServlet</servlet-name> <url-pattern>/jbpm/deployprocess</url-pattern> </servlet-mapping> <session-config> <session-timeout>60</session-timeout> </session-config> <welcome-file-list> <welcome-file>index.jsp</welcome-file> </welcome-file-list> <error-page> <exception-type>java.lang.Exception</exception-type> <location>/jsp/error.jsp</location> </error-page> </web-app>ldap.authentifcation-context.xml :
<?xml version='1.0' encoding='UTF-8'?><!DOCTYPE beans PUBLIC '-//SPRING//DTD BEAN//EN' 'http://www.springframework.org/dtd/spring-beans.dtd'><beans> <!– DAO that rejects changes - LDAP is read only at the moment. It does allow users to be deleted with out warnings from the UI. –> <bean name="authenticationDao" class="org.alfresco.repo.security.authentication.DefaultMutableAuthenticationDao" > <property name="allowDeleteUser"> <value>true</value> </property> </bean> <!– LDAP authentication configuration –> <!– You can also use JAAS authentication for Kerberos against Active Directory or NTLM if you also require single sign on from the web browser. You do not have to use LDAP authentication to synchronise groups and users from an LDAP store if it supports other authentication routes, like Active Directory. –> <bean id="authenticationComponentImpl" class="org.alfresco.repo.security.authentication.ldap.LDAPAuthenticationComponentImpl"> <property name="LDAPInitialDirContextFactory"> <ref bean="ldapInitialDirContextFactory"/> </property> <property name="userNameFormat"> <!– This maps between what the user types in and what is passed through to the underlying LDAP authentication. "%s" - the user id is passed through without modification. Used for LDAP authentication such as DIGEST-MD5, anything that is not "simple". "cn=%s,ou=London,dc=company,dc=com" - If the user types in "Joe Bloggs" the authentricate as "cn=Joe Bloggs,ou=London,dc=company,dc=com" Usually for simple authentication. –> <value>cn=%s,OU=Utilisateurs,OU=**,DC=**,DC=Intra</value> </property> </bean> <!– This bean is used to support general LDAP authentication. It is also used to provide read only access to users and groups to pull them out of the LDAP reopsitory –> <bean id="ldapInitialDirContextFactory" class="org.alfresco.repo.security.authentication.ldap.LDAPInitialDirContextFactoryImpl"> <property name="initialDirContextEnvironment"> <map> <!– The LDAP provider –> <entry key="java.naming.factory.initial"> <value>com.sun.jndi.ldap.LdapCtxFactory</value> </entry> <!– The url to the LDAP server –> <!– Note you can use space separated urls - they will be tried in turn until one works –> <!– This could be used to authenticate against one or more ldap servers (you will not know which one ….) –> <entry key="java.naming.provider.url"> <value>ldap://**:389</value> </entry> <!– The authentication mechanism to use –> <!– Some sasl authentication mechanisms may require a realm to be set –> <!– java.naming.security.sasl.realm –> <!– The available options will depend on your LDAP provider –> <entry key="java.naming.security.authentication"> <value>DIGEST-MD5</value> </entry> <!– The id of a user who can read group and user information –> <!– This does not go through the pattern substitution defined above and is used "as is" –> <entry key="java.naming.security.principal"> <value>**</value> </entry> <!– The password for the user defined above –> <entry key="java.naming.security.credentials"> <value>**</value> </entry> </map> </property> </bean> <!– Ldap Syncronisation support –> <!– There can be more than one stack of beans that import users or groups. For example, it may be easier to have a version of ldapPeopleExportSource, and associated beans, for each sub-tree of your ldap directory from which you want to import users. You could then limit users to be imported from two or more sub tress and ignore users found else where. The same applies to the import of groups. The defaults shown below are for OpenLDAP. –> <!– Extract user information from LDAP and transform this to XML –> <bean id="ldapPeopleExportSource" class="org.alfresco.repo.security.authentication.ldap.LDAPPersonExportSource"> <!– The query to select objects that represent the users to import. For Open LDAP, using a basic schema, the following is probably what you want: (objectclass=inetOrgPerson) For Active Directory: (objectclass=user) –> <property name="personQuery"> <value>(objectclass=user)</value> </property> <!– The seach base restricts the LDAP query to a sub section of tree on the LDAP server. –> <property name="searchBase"> <value>OU=Utilisateurs,OU=**,DC=**,DC=Intra</value> </property> <!– The unique identifier for the user. THIS MUST MATCH WHAT THE USER TYPES IN AT THE LOGIN PROMPT For simple LDAP authentication this is likely to be "cn" or, less friendly, "distinguishedName" In OpenLDAP, using other authentication mechanisms "uid", but this depends on how you map from the id in the LDAP authentication request to search for the inetOrgPerson against which to authenticate. In Active Directory this is most likely to be "sAMAccountName" This property is mandatory and must appear on all users found by the query defined above. –> <property name="userIdAttributeName"> <value>sAMAccountName</value> </property> <!– Services –> <property name="LDAPInitialDirContextFactory"> <ref bean="ldapInitialDirContextFactory"/> </property> <property name="personService"> <ref bean="personService"></ref> </property> <property name="namespaceService"> <ref bean="namespaceService"/> </property> <!– This property defines a mapping between attributes held on LDAP user objects and the properties of user objects held in the repository. The key is the QName of an attribute in the repository, the value is the attribute name from the user/inetOrgPerson/.. object in the LDAP repository. –> <property name="attributeMapping"> <map> <entry key="cm:userName"> <!– Must match the same attribute as userIdAttributeName –> <value>sAMAccountName</value> </entry> <entry key="cm:firstName"> <!– OpenLDAP: "givenName" –> <!– Active Directory: "givenName" –> <value>givenName</value> </entry> <entry key="cm:lastName"> <!– OpenLDAP: "sn" –> <!– Active Directory: "sn" –> <value>sn</value> </entry> <entry key="cm:email"> <!– OpenLDAP: "mail" –> <!– Active Directory: "???" –> <value>mail</value> </entry> <entry key="cm:organizationId"> <!– OpenLDAP: "o" –> <!– Active Directory: "???" –> <value>company</value> </entry> <!– Always use the default –> <entry key="cm:homeFolderProvider"> <null/> </entry> </map> </property> <!– Set a default home folder provider –> <!– Defaults only apply for values above –> <property name="attributeDefaults"> <map> <entry key="cm:homeFolderProvider"> <value>personalHomeFolderProvider</value> </entry> </map> </property> </bean> <!– Extract group information from LDAP and transform this to XML –> <bean id="ldapGroupExportSource" class="org.alfresco.repo.security.authentication.ldap.LDAPGroupExportSource"> <!– The query to select objects that represent the groups to import. For Open LDAP, using a basic schema, the following is probably what you want: (objectclass=groupOfNames) For Active Directory: (objectclass=group) –> <property name="groupQuery"> <value>(objectclass=group)</value> </property> <!– The seach base restricts the LDAP query to a sub section of tree on the LDAP server. –> <property name="searchBase"> <value>OU=Groupes,OU=**,DC=**,DC=Intra</value> </property> <!– The unique identifier for the user. This must match the userIdAttributeName on the ldapPeopleExportSource bean above. –> <property name="userIdAttributeName"> <value>sAMAccountName</value> </property> <!– An attribute that is a unique identifier for each group found. This is also the name of the group with the current group implementation. This is mandatory for any groups found. OpenLDAP: "cn" as it is mandatory on groupOfNames Active Directory: "cn" –> <property name="groupIdAttributeName"> <value>cn</value> </property> <!– The objectClass attribute for group members. For each member of a group, the distinguished name is given. The object is looked up by its DN. If the object is of this class it is treated as a group. –> <property name="groupType"> <value>groupOfNames</value> </property> <!– The objectClass attribute for person members. For each member of a group, the distinguished name is given. The object is looked up by its DN. If the object is of this class it is treated as a person. –> <property name="personType"> <value>inetOrgPerson</value> </property> <property name="LDAPInitialDirContextFactory"> <ref bean="ldapInitialDirContextFactory"/> </property> <property name="namespaceService"> <ref bean="namespaceService"/> </property> <!– The repeating attribute on group objects (found by query or as sub groups) used to define membership of the group. This is assumed to hold distinguished names of other groups or users/people; the above types are used to determine this. OpenLDAP: "member" as it is mandatory on groupOfNames Active Directory: "member" –> <property name="memberAttribute"> <value>member</value> </property> <property name="authorityDAO"> <ref bean="authorityDAO"/> </property> </bean> <!– Job definitions to import LDAP people and groups –> <!– The triggers register themselves with the scheduler –> <!– You may comment in the default scheduler to enable these triggers –> <!– If a cron base trigger is what you want seee scheduled-jobs-context.xml for examples. –> <!– Trigger to load poeple –> <!– Note you can have more than one initial (context, trigger, import job and export source) set –> <!– This would allow you to load people from more than one ldap store –> <bean id="ldapPeopleTrigger" class="org.alfresco.util.TriggerBean"> <property name="jobDetail"> <bean id="ldapPeopleJobDetail" class="org.springframework.scheduling.quartz.JobDetailBean"> <property name="jobClass"> <value>org.alfresco.repo.importer.ImporterJob</value> </property> <property name="jobDataAsMap"> <map> <entry key="bean"> <ref bean="ldapPeopleImport"/> </entry> </map> </property> </bean> </property> <!– Start after 5 minutes of starting the repository –> <property name="startDelay"> <value>300000</value> </property> <!– Repeat every hour –> <property name="repeatInterval"> <value>3600000</value> </property> <!– Commented out to disable <property name="scheduler"> <ref bean="schedulerFactory" /> </property> –> </bean> <bean id="ldapGroupTrigger" class="org.alfresco.util.TriggerBean"> <property name="jobDetail"> <bean id="ldapGroupJobDetail" class="org.springframework.scheduling.quartz.JobDetailBean"> <property name="jobClass"> <value>org.alfresco.repo.importer.ImporterJob</value> </property> <property name="jobDataAsMap"> <map> <entry key="bean"> <ref bean="ldapGroupImport"/> </entry> </map> </property> </bean> </property> <!– Start after 5 minutes of starting the repository –> <property name="startDelay"> <value>300000</value> </property> <!– Repeat every hour –> <property name="repeatInterval"> <value>3600000</value> </property> <!– Commented out to disable <property name="scheduler"> <ref bean="schedulerFactory" /> </property> –> </bean> <!– The bean that imports xml describing people –> <bean id="ldapPeopleImport" class="org.alfresco.repo.importer.ExportSourceImporter"> <property name="importerService"> <ref bean="importerComponentWithBehaviour"/> </property> <property name="transactionService"> <ref bean="transactionComponent"/> </property> <property name="authenticationComponent"> <ref bean="authenticationComponent"/> </property> <property name="exportSource"> <ref bean="ldapPeopleExportSource"/> </property> <!– The store that contains people - this should not be changed –> <property name="storeRef"> <value>${spaces.store}</value> </property> <!– The location of people nodes within the store defined above - this should not be changed –> <property name="path"> <value>/${system.system_container.childname}/${system.people_container.childname}</value> </property> <!– If true, clear all existing people before import, if false update/add people from the xml –> <property name="clearAllChildren"> <value>false</value> </property> <property name="nodeService"> <ref bean="nodeService"/> </property> <property name="searchService"> <ref bean="searchService"/> </property> <property name="namespacePrefixResolver"> <ref bean="namespaceService"/> </property> <property name="caches"> <set> <ref bean="permissionsAccessCache"/> </set> </property> </bean> <!– The bean that imports xml descibing groups –> <bean id="ldapGroupImport" class="org.alfresco.repo.importer.ExportSourceImporter"> <property name="importerService"> <ref bean="importerComponentWithBehaviour"/> </property> <property name="transactionService"> <ref bean="transactionComponent"/> </property> <property name="authenticationComponent"> <ref bean="authenticationComponent"/> </property> <property name="exportSource"> <ref bean="ldapGroupExportSource"/> </property> <!– The store that contains group information - this should not be changed –> <property name="storeRef"> <value>${alfresco_user_store.store}</value> </property> <!– The location of group information in the store above - this should not be changed –> <property name="path"> <value>/${alfresco_user_store.system_container.childname}/${alfresco_user_store.authorities_container.childname}</value> </property> <!– If true, clear all existing groups before import, if false update/add groups from the xml –> <property name="clearAllChildren"> <value>true</value> </property> <property name="nodeService"> <ref bean="nodeService"/> </property> <property name="searchService"> <ref bean="searchService"/> </property> <property name="namespacePrefixResolver"> <ref bean="namespaceService"/> </property> <!– caches to clear on import of groups –> <property name="caches"> <set> <ref bean="userToAuthorityCache"/> <ref bean="permissionsAccessCache"/> </set> </property> <!– userToAuthorityCache –> </bean> </beans><?xml version='1.0' encoding='UTF-8'?><!DOCTYPE beans PUBLIC '-//SPRING//DTD BEAN//EN' 'http://www.springframework.org/dtd/spring-beans.dtd'><beans> <bean id="authenticationDao" class="org.alfresco.repo.security.authentication.ntlm.NullMutableAuthenticationDao"> <property name="nodeService"> <ref bean="nodeService" /> </property> </bean> <!– Note from V2.0 the bean id must be authenticationComponent –> <bean id="authenticationComponentImpl" class="org.alfresco.repo.security.authentication.ntlm.NTLMAuthenticationComponentImpl"> <property name="servers"> <value>192.90.**</value> </property> <property name="personService"> <ref bean="personService" /> </property> <property name="nodeService"> <ref bean="nodeService" /> </property> <property name="guestAccess"> <value>false</value> </property> </bean> </beans>Faut t'il modifier un autre fichier pour la synchro LDAP ? S'il vous plait, ne me balancé pas le lien vers le wiki…j'ai lu en long, en large….Merci de votre aide
Bonjour, merci de ta réponse
Dans le fichier Log, rien concernant LDAP…:/
Je vous remet le fichier ldap…modifié..
Dans le fichier Log, rien concernant LDAP…:/
Je vous remet le fichier ldap…modifié..
<?xml version='1.0' encoding='UTF-8'?><!DOCTYPE beans PUBLIC '-//SPRING//DTD BEAN//EN' 'http://www.springframework.org/dtd/spring-beans.dtd'><beans> <!– DAO that rejects changes - LDAP is read only at the moment. It does allow users to be deleted with out warnings from the UI. –> <!– <bean name="authenticationDao" class="org.alfresco.repo.security.authentication.DefaultMutableAuthenticationDao" > <property name="allowDeleteUser"> <value>true</value> </property> </bean> –> <!– LDAP authentication configuration –> <!– You can also use JAAS authentication for Kerberos against Active Directory or NTLM if you also require single sign on from the web browser. You do not have to use LDAP authentication to synchronise groups and users from an LDAP store if it supports other authentication routes, like Active Directory. –> <!– <bean id="authenticationComponentImpl" class="org.alfresco.repo.security.authentication.ldap.LDAPAuthenticationComponentImpl"> <property name="LDAPInitialDirContextFactory"> <ref bean="ldapInitialDirContextFactory"/> </property> <property name="userNameFormat"> –> <!– This maps between what the user types in and what is passed through to the underlying LDAP authentication. "%s" - the user id is passed through without modification. Used for LDAP authentication such as DIGEST-MD5, anything that is not "simple". "cn=%s,ou=London,dc=company,dc=com" - If the user types in "Joe Bloggs" the authentricate as "cn=Joe Bloggs,ou=London,dc=company,dc=com" Usually for simple authentication. –> <!– <value>cn=%s,OU=Utilisateurs,OU=**,DC=**,DC=Intra</value> </property> </bean> –> <!– This bean is used to support general LDAP authentication. It is also used to provide read only access to users and groups to pull them out of the LDAP reopsitory –> <bean id="ldapInitialDirContextFactory" class="org.alfresco.repo.security.authentication.ldap.LDAPInitialDirContextFactoryImpl"> <property name="initialDirContextEnvironment"> <map> <!– The LDAP provider –> <entry key="java.naming.factory.initial"> <value>com.sun.jndi.ldap.LdapCtxFactory</value> </entry> <!– The url to the LDAP server –> <!– Note you can use space separated urls - they will be tried in turn until one works –> <!– This could be used to authenticate against one or more ldap servers (you will not know which one ….) –> <entry key="java.naming.provider.url"> <value>ldap://**:389</value> </entry> <!– The authentication mechanism to use –> <!– Some sasl authentication mechanisms may require a realm to be set –> <!– java.naming.security.sasl.realm –> <!– The available options will depend on your LDAP provider –> <entry key="java.naming.security.authentication"> <value>simple</value> </entry> <!– The id of a user who can read group and user information –> <!– This does not go through the pattern substitution defined above and is used "as is" –> <entry key="java.naming.security.principal"> <value>CN=administrateur,CN=Users,DC=**,DC=Intra</value> </entry> <!– The password for the user defined above –> <entry key="java.naming.security.credentials"> <value>**</value> </entry> </map> </property> </bean> <!– Ldap Syncronisation support –> <!– There can be more than one stack of beans that import users or groups. For example, it may be easier to have a version of ldapPeopleExportSource, and associated beans, for each sub-tree of your ldap directory from which you want to import users. You could then limit users to be imported from two or more sub tress and ignore users found else where. The same applies to the import of groups. The defaults shown below are for OpenLDAP. –> <!– Extract user information from LDAP and transform this to XML –> <bean id="ldapPeopleExportSource" class="org.alfresco.repo.security.authentication.ldap.LDAPPersonExportSource"> <!– The query to select objects that represent the users to import. For Open LDAP, using a basic schema, the following is probably what you want: (objectclass=inetOrgPerson) For Active Directory: (objectclass=user) –> <property name="personQuery"> <value>(objectclass=user)</value> </property> <!– The seach base restricts the LDAP query to a sub section of tree on the LDAP server. –> <property name="searchBase"> <value>OU=Utilisateurs,OU=**,DC=**,DC=Intra</value> </property> <!– The unique identifier for the user. THIS MUST MATCH WHAT THE USER TYPES IN AT THE LOGIN PROMPT For simple LDAP authentication this is likely to be "cn" or, less friendly, "distinguishedName" In OpenLDAP, using other authentication mechanisms "uid", but this depends on how you map from the id in the LDAP authentication request to search for the inetOrgPerson against which to authenticate. In Active Directory this is most likely to be "sAMAccountName" This property is mandatory and must appear on all users found by the query defined above. –> <property name="userIdAttributeName"> <value>sAMAccountName</value> </property> <!– Services –> <property name="LDAPInitialDirContextFactory"> <ref bean="ldapInitialDirContextFactory"/> </property> <property name="personService"> <ref bean="personService"></ref> </property> <property name="namespaceService"> <ref bean="namespaceService"/> </property> <!– This property defines a mapping between attributes held on LDAP user objects and the properties of user objects held in the repository. The key is the QName of an attribute in the repository, the value is the attribute name from the user/inetOrgPerson/.. object in the LDAP repository. –> <property name="attributeMapping"> <map> <entry key="cm:userName"> <!– Must match the same attribute as userIdAttributeName –> <value>sAMAccountName</value> </entry> <entry key="cm:firstName"> <!– OpenLDAP: "givenName" –> <!– Active Directory: "givenName" –> <value>givenName</value> </entry> <entry key="cm:lastName"> <!– OpenLDAP: "sn" –> <!– Active Directory: "sn" –> <value>sn</value> </entry> <entry key="cm:email"> <!– OpenLDAP: "mail" –> <!– Active Directory: "???" –> <value>mail</value> </entry> <entry key="cm:organizationId"> <!– OpenLDAP: "o" –> <!– Active Directory: "???" –> <value>company</value> </entry> <!– Always use the default –> <entry key="cm:homeFolderProvider"> <null/> </entry> </map> </property> <!– Set a default home folder provider –> <!– Defaults only apply for values above –> <property name="attributeDefaults"> <map> <entry key="cm:homeFolderProvider"> <value>personalHomeFolderProvider</value> </entry> </map> </property> </bean> <!– Extract group information from LDAP and transform this to XML –> <bean id="ldapGroupExportSource" class="org.alfresco.repo.security.authentication.ldap.LDAPGroupExportSource"> <!– The query to select objects that represent the groups to import. For Open LDAP, using a basic schema, the following is probably what you want: (objectclass=groupOfNames) For Active Directory: (objectclass=group) –> <property name="groupQuery"> <value>(objectclass=group)</value> </property> <!– The seach base restricts the LDAP query to a sub section of tree on the LDAP server. –> <property name="searchBase"> <value>OU=Groupes,OU=**,DC=**,DC=Intra</value> </property> <!– The unique identifier for the user. This must match the userIdAttributeName on the ldapPeopleExportSource bean above. –> <property name="userIdAttributeName"> <value>sAMAccountName</value> </property> <!– An attribute that is a unique identifier for each group found. This is also the name of the group with the current group implementation. This is mandatory for any groups found. OpenLDAP: "cn" as it is mandatory on groupOfNames Active Directory: "cn" –> <property name="groupIdAttributeName"> <value>cn</value> </property> <!– The objectClass attribute for group members. For each member of a group, the distinguished name is given. The object is looked up by its DN. If the object is of this class it is treated as a group. –> <property name="groupType"> <value>groupOfNames</value> </property> <!– The objectClass attribute for person members. For each member of a group, the distinguished name is given. The object is looked up by its DN. If the object is of this class it is treated as a person. –> <property name="personType"> <value>inetOrgPerson</value> </property> <property name="LDAPInitialDirContextFactory"> <ref bean="ldapInitialDirContextFactory"/> </property> <property name="namespaceService"> <ref bean="namespaceService"/> </property> <!– The repeating attribute on group objects (found by query or as sub groups) used to define membership of the group. This is assumed to hold distinguished names of other groups or users/people; the above types are used to determine this. OpenLDAP: "member" as it is mandatory on groupOfNames Active Directory: "member" –> <property name="memberAttribute"> <value>member</value> </property> <property name="authorityDAO"> <ref bean="authorityDAO"/> </property> </bean> <!– Job definitions to import LDAP people and groups –> <!– The triggers register themselves with the scheduler –> <!– You may comment in the default scheduler to enable these triggers –> <!– If a cron base trigger is what you want seee scheduled-jobs-context.xml for examples. –> <!– Trigger to load poeple –> <!– Note you can have more than one initial (context, trigger, import job and export source) set –> <!– This would allow you to load people from more than one ldap store –> <bean id="ldapPeopleTrigger" class="org.alfresco.util.TriggerBean"> <property name="jobDetail"> <bean id="ldapPeopleJobDetail" class="org.springframework.scheduling.quartz.JobDetailBean"> <property name="jobClass"> <value>org.alfresco.repo.importer.ImporterJob</value> </property> <property name="jobDataAsMap"> <map> <entry key="bean"> <ref bean="ldapPeopleImport"/> </entry> </map> </property> </bean> </property> <!– Start after 5 minutes of starting the repository –> <property name="startDelay"> <value>300000</value> </property> <!– Repeat every hour –> <property name="repeatInterval"> <value>3600000</value> </property> <!– Commented out to disable <property name="scheduler"> <ref bean="schedulerFactory" /> </property> –> </bean> <bean id="ldapGroupTrigger" class="org.alfresco.util.TriggerBean"> <property name="jobDetail"> <bean id="ldapGroupJobDetail" class="org.springframework.scheduling.quartz.JobDetailBean"> <property name="jobClass"> <value>org.alfresco.repo.importer.ImporterJob</value> </property> <property name="jobDataAsMap"> <map> <entry key="bean"> <ref bean="ldapGroupImport"/> </entry> </map> </property> </bean> </property> <!– Start after 5 minutes of starting the repository –> <property name="startDelay"> <value>300000</value> </property> <!– Repeat every hour –> <property name="repeatInterval"> <value>3600000</value> </property> <!– Commented out to disable <property name="scheduler"> <ref bean="schedulerFactory" /> </property> –> </bean> <!– The bean that imports xml describing people –> <bean id="ldapPeopleImport" class="org.alfresco.repo.importer.ExportSourceImporter"> <property name="importerService"> <ref bean="importerComponentWithBehaviour"/> </property> <property name="transactionService"> <ref bean="transactionComponent"/> </property> <property name="authenticationComponent"> <ref bean="authenticationComponent"/> </property> <property name="exportSource"> <ref bean="ldapPeopleExportSource"/> </property> <!– The store that contains people - this should not be changed –> <property name="storeRef"> <value>${spaces.store}</value> </property> <!– The location of people nodes within the store defined above - this should not be changed –> <property name="path"> <value>/${system.system_container.childname}/${system.people_container.childname}</value> </property> <!– If true, clear all existing people before import, if false update/add people from the xml –> <property name="clearAllChildren"> <value>false</value> </property> <property name="nodeService"> <ref bean="nodeService"/> </property> <property name="searchService"> <ref bean="searchService"/> </property> <property name="namespacePrefixResolver"> <ref bean="namespaceService"/> </property> <property name="caches"> <set> <ref bean="permissionsAccessCache"/> </set> </property> </bean> <!– The bean that imports xml descibing groups –> <bean id="ldapGroupImport" class="org.alfresco.repo.importer.ExportSourceImporter"> <property name="importerService"> <ref bean="importerComponentWithBehaviour"/> </property> <property name="transactionService"> <ref bean="transactionComponent"/> </property> <property name="authenticationComponent"> <ref bean="authenticationComponent"/> </property> <property name="exportSource"> <ref bean="ldapGroupExportSource"/> </property> <!– The store that contains group information - this should not be changed –> <property name="storeRef"> <value>${alfresco_user_store.store}</value> </property> <!– The location of group information in the store above - this should not be changed –> <property name="path"> <value>/${alfresco_user_store.system_container.childname}/${alfresco_user_store.authorities_container.childname}</value> </property> <!– If true, clear all existing groups before import, if false update/add groups from the xml –> <property name="clearAllChildren"> <value>true</value> </property> <property name="nodeService"> <ref bean="nodeService"/> </property> <property name="searchService"> <ref bean="searchService"/> </property> <property name="namespacePrefixResolver"> <ref bean="namespaceService"/> </property> <!– caches to clear on import of groups –> <property name="caches"> <set> <ref bean="userToAuthorityCache"/> <ref bean="permissionsAccessCache"/> </set> </property> <!– userToAuthorityCache –> </bean> </beans>… blabla … <!– Commented out to disable <property name="scheduler"> <ref bean="schedulerFactory" /> </property> –> </bean>… blabla …
