Hi,I use Alfresco 2.1.0 with authetication LDAP,the probleme it's that alfresco creat un personnel space and a compte in eache autehtication user,i want to deny this comportement and use just authentication and delegate creating compte to administrateur .
<!– =================================================================== –> <!– This file contains the bean definitions that support authentication –> <!– =================================================================== –>
<!– –> <!– Acegi is used for authentication and protecting method calls on public –> <!– services. To do this requires our authentication mechanism to work –> <!– within the acegi framework. –> <!– –> <!– It is important to decide if user names are case sensitive or not. –> <!– This is configured in repository.properties. –> <!– –> <!– –> <!– TODO: –> <!– –> <!– The transactional wrappers should be removed from the beans in this –> <!– file. This should be done in the public services definitions. –> <!– This requires some tests to be fixed up. –> <!– –> <beans> <!– –> <!– The Acegi authentication manager. –> <!– –> <!– Provders are asked to authenticate in order. –> <!– First, is a provider that checks if an acegi authentication object –> <!– is already bound to the executing thread. If it is, and it is set –> <!– as authenticated then no further authentication is required. If –> <!– this is absent, Acegi validates the password for every method –> <!– invocation, which is too CPU expensive. If we set an –> <!– authentication based on a ticket etc …. or we want to set the –> <!– the system user as the current user … we do not have the –> <!– password. So if we have set an authentication and set it as –> <!– authenticated that is sufficient to validate the user. –> <!– –> <!– If the authentication bound to the current thread is not set as –> <!– authenticated the standard Acegi DAO Authentication provider –> <!– is used to authenticate. –> <!– –>
<!– An authentication Provider that just believes authentications –> <!– bound to the local thread are valid if they are set as –> <!– authenticated. –>
<!– The DAO also acts as a salt provider. –> <alias alias="saltSource" name="authenticationDao"/>
<!– Passwords are encoded using MD4 –> <!– This is not ideal and only done to be compatible with NTLM –> <!– authentication against the default authentication mechanism. –>
<!– The Authentication Service implementation. –> <!– –> <!– This delegates its work to two services: –> <!– an AuthenticationComponent and a MutableAuthenticationDAO. –> <!– –> <!– The permissions service is required so that permissions can be –> <!– cleaned up when a user is deleted. –> <alias name="authenticationService" alias="authenticationServiceImpl"/> <!– TODO: Remove –> <bean id="authenticationService" class="org.alfresco.repo.security.authentication.AuthenticationServiceImpl"> <property name="authenticationDao"> <ref bean="authenticationDao" /> </property> <property name="ticketComponent"> <ref bean="ticketComponent" /> </property> <property name="authenticationComponent"> <ref bean="authenticationComponent" /> </property> </bean>
<!– Simple Authentication component that rejects all authentication requests –> <!– Use this defintion for Novell IChain integration. –> <!– It should never go to the login screen so this is not required –> <!– <bean id="authenticationComponent" class="org.alfresco.repo.security.authentication.SimpleAcceptOrRejectAllAuthenticationComponentImpl"> <property name="accept"> <value>true</value> </property> </bean> –>
<!– The person service. –>
<bean id="personService" class="org.alfresco.repo.security.person.PersonServiceImpl" init-method="init"> <property name="nodeService"> <ref bean="nodeService" /> </property> <property name="searchService"> <ref bean="admSearchService" /> </property> <property name="permissionServiceSPI"> <ref bean="permissionServiceImpl" /> </property> <property name="authorityService"> <ref bean="authorityService" /> </property> <property name="namespacePrefixResolver"> <ref bean="namespaceService" /> </property> <property name="policyComponent"> <ref bean="policyComponent"/> </property> <property name="personCache"> <ref bean="personCache" /> </property> <!– Configurable properties. –> <!– –> <!– TODO: –> <!– Add support for creating real home spaces adn setting –> <!– permissions on the hame space and people created. –> <!– –> <!– The store in which people are persisted. –> <property name="storeUrl"> <value>${spaces.store}</value> </property> <!– Some authentication mechanisms may need to create people –> <!– in the repository on demand. This enables that feature. –> <!– If dsiabled an error will be generated for missing –> <!– people. If enabled then a person will be created and –> <!– persisted. –> <!– Valid values are –> <!– ${server.transaction.allow-writes} –> <!– false –> <property name="createMissingPeople"> <value>${server.transaction.allow-writes}</value> </property> <property name="userNamesAreCaseSensitive"> <value>${user.name.caseSensitive}</value> </property> <!– New properties after 1.4.0 to deal with duplicate user ids when found –> <property name="processDuplicates"> <value>true</value> </property> <!– one of: LEAVE, SPLIT, DELETE –> <property name="duplicateMode"> <value>SPLIT</value> </property> <property name="lastIsBest"> <value>true</value> </property> <property name="includeAutoCreated"> <value>false</value> </property> </bean>
same problem here.. The LDAP sync'ed all the groups and user but when someone log-in, it look like he delete the user and replace it by the userId and create him a personal space with his usrID..