Hi Syncopers, we have a password issue to be discussed and managed asap. Currently, every time user's resource set is updated a new user password specification is required. From my point of view this couldn't be acceptable: a new password should be required just in case of adding of a new resource requiring password. Do you have any idea about how we can do this?
The same behavior is applied in case of an user update coming from a synchronization. If during synchronization an user must be updated by adding a new resource to its external resource set (may be implied by a user template) new password specification is always required. Currently we'll get a failure in this scenario .... Do you have any idea about how we can generate a new password just for new external resources requiring it? Guys, I ask you your opinions in order to open a new issue to tune these behaviors. Please, let me have your feedback. Regards, F.
