- 
    
Bug
 - 
    Resolution: Fixed
 - 
    
Major
 - 
    None
 
- 
        4.5 M3
 
How to reproduce:
- Create a user synchro definition
 - Launch the synchronisation
	
- The "user" data of each user content is well filled with corresponding login and population => OK
 
 - Modify the user data of a synchronized user
 - Launch the synchornization again
	
- The user content that was modified is KO:
		
- its data user still contains the previous modification
 - it has a new login data containing the login and population of the synchronization
 
 
 - The user content that was modified is KO:
		
 
- Bloque
 - 
                    
UD-203 Delete old API's warnings
-         
 - Closed
 
 -