Currently, during propagation (CREATE or UPDATE) password will pe propagated (if and only if it is available) also in case it is not explicitely requested. This behavior has to be changed because it can cause unwanted password replaces in case of update operation.
1. change password encryption to AES.
2. change users password.
3. assigne resource: password is propagated as expected.
4. change some other attribute and saved: again the password is propagated. This is a potential problem: if user later change the password in the resource, syncope should not overwrite passowrd after that.