cancel
Showing results for 
Search instead for 
Did you mean: 

Removing users from repository during LDAP-synchronization

bernard
Champ in-the-making
Champ in-the-making
Hello,

I've problem with Alfresco 4.2.c.
I'd like to ask one question to specialists.

We have LDAP-synchronization users and groups in Alfresco (FULL and Differential With Removals). Now if I remove user from AD and he have role Editor in different documents Alfresco, Alfresco can't remove it during synchronization.
There is string <strong>synchronization.allowDeletions=true</strong> in the properties of file default-synchronization.

Our developers of content in Alfresco say that is normally because user-Editor is attached to document in repository. And we should change editor on other real user (in AD) in this document, then Alfresco can remove it.

Is this normal situation for process removing users during AD-sinchronization in Alfresco?
Can I configure Alfresco for removing local users if they have different roles in documents?

Thank you for reply.
6 REPLIES 6

mlagneaux
Champ on-the-rise
Champ on-the-rise
Hi,

I think that's a normal situation. Your users are removed by Alfresco but, if a node has one of the removed users login in creator or modifier property, Alfresco is going to create a "ghost" user with this login.

Take a look at one of the removed users in the node browser. I think it will be empty : no email address, no last name, …

bernard
Champ in-the-making
Champ in-the-making
Hello,

Thank you for your reply.
If I look one of the removed user I can see attributes: email, last name..

I 'd like to ask also other question, is parametr <strong>true</strong> for string <strong>synchronization.allowDeletions</strong> remove only users that are not have roles in any documents ?   

bernard
Champ in-the-making
Champ in-the-making
Is that realy difficult question?

bhavikp
Champ on-the-rise
Champ on-the-rise
Hi Bernard,

A scheduled job triggers synchronization in differential with removals mode every 24 hours.

What is the value of your following properties.

synchronization.import.cron

bernard
Champ in-the-making
Champ in-the-making
Hi Bhavikp,

synchronization.import.cron=0 0/50 * * * ?
But I think, that's not the reason, I tried to use different parametres of synchronization (full or differential with removals).

bhavikp
Champ on-the-rise
Champ on-the-rise
ldap.synchronization.personDifferentialQuery

The query to select objects that represent the users to import that have changed since a certain time.