cancel
Showing results for 
Search instead for 
Did you mean: 

Full AD Synchronisation not removing user property values

alfresconewbie
Champ in-the-making
Champ in-the-making
Alfresco CE 4.2f

We have full sync configured between Alfresco and Active Directory.

When users are created or deleted from Active Directory the changes are correctly reflected in Alfresco.  However, I have noticed one issue regarding user attribute updates.

We have created a custom map (custom-ldap-context.xml) to allow a users mobile telephone number to be sync'd to Alfresco

        <property name="personAttributeMapping">
            <map>
                 <!– CUSTOM ENTRY KEYS –>
                <entry key="cm:mobile">
                    <!– Active Directory: "mobile" –>
                    <value>${ldap.synchronization.userMobileAttributeName}</value>
                </entry>



if a user's mobile number is entered in active directory and the full sync runs the number is correctly reflected in Alfresco, same if we change their number in Active Directory the new number is correctly sync'd.  However, if I remove someone's mobile number in Active Directory then run a full synchronisation the change isn't reflected in Alfresco.

So…

Person A created in Active directory without a mobile phone number > After Full Sync = person correctly appears in Alfresco

Person A's mobile phone number updated to 0000000000001 in active directory  > After Full Sync = person correctly appears in Alfresco with mobile number 0000000000001

Person A's mobile phone number updated to 0000000000002 in active directory  > After Full Sync = person correctly appears in Alfresco with mobile number 0000000000002

Person A's mobile phone number removed from active directory  > After Full Sync = person mobile number incorrectly shows as 0000000000002

It seems like when a user attribute is removed from Active Directory (Not just their mobile number) that the changes aren't reflected in Alfresco following a full sync.



1 REPLY 1

mrogers
Star Contributor
Star Contributor
Yes that's probably expected functionality. 

It would be dangerous to do otherwise,  if a property does not exist in AD then delete it in alfresco.