cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to delete User...???

prck
Champ in-the-making
Champ in-the-making
Hi,

My database has been modified by a plugin. Now, there is at least 2 or 3 occurrences by user (with the same user name). When I try to delete one user, i get the folowing message :

Failed to delete User due to error: Found more than one user for ***** (case insensitive)

So how to delete these users ?

Thanks
Prck
6 REPLIES 6

ljones1009
Champ in-the-making
Champ in-the-making
I'm getting the same thing.  Would anyone happen to have the answer for this?

andy
Champ on-the-rise
Champ on-the-rise
Hi

Which version of Afrecso are you using?

V1.4 should deal with duplicate users.

How exactly did this plugin change the database?
What does it do?

Regards

Andy

ribz33
Champ on-the-rise
Champ on-the-rise
I have same problem also !

im using 1.4.0 version on tomcat
i have test with a light version :
- ldap import users and groups
- chaining authentification
- original war
- empty repository

and i have 2 same users for each user after user import.

prck
Champ in-the-making
Champ in-the-making
I'm using the 1.4 tomcat verson. In my    tomcat/shared/classes/alfresco/extension/ldap-authentication-context.xml, I have found the clearAllchildren propetiy :



<property name="clearAllChildren">
       <value>false</value>
</property>


I have solved the problem by setting this property to true.

ribz33
Champ on-the-rise
Champ on-the-rise
But me i have Alfresco users and Active Directory users if i "clearAllChildren" i lose all my Alfresco users…

But thx about your idea i will test it and i will think about it maybe i will use only AD like directory.

andy
Champ on-the-rise
Champ on-the-rise
Hi

I would not set the <property name="clearAllChildren"> option to true unless you have guest and admin defined in your LDAP import or you will loose these users. You will also throw away all user settings each time (e.g preferences).

The LDAP import should find and update existing users. It uses the uid defined in the import file as key. Check your config files to make sure the person uid always uses the correct attribute from the LDAP user object. It is possible to misconfigure this and get the behaviour you describe. This is set in number of beans.  (Making this easier is on the list.)

Regards

Andy