[
https://issues.apache.org/jira/browse/SYNCOPE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047711#comment-14047711
]
Marco Di Sabatino Di Diodoro commented on SYNCOPE-391:
------------------------------------------------------
Propagation: the propagation of the password to the resource is determined by
the configuration of the password policy, in particular if there exists at
least a password policy that says to store the password, Syncope must store it
inside the repository.
Sync: if you don't need to store the password in the internal repository,
Syncope should not create the generated password.
> Make password management optional
> ---------------------------------
>
> Key: SYNCOPE-391
> URL: https://issues.apache.org/jira/browse/SYNCOPE-391
> Project: Syncope
> Issue Type: Improvement
> Reporter: Francesco Chicchiriccò
> Assignee: Andrea Patricelli
> Fix For: 1.2.0
>
>
> Currently, SyncopeUser#password is annotated as @NotNull - this has several
> consequences to propagation / synchronization and even to admin console.
> However, it would be a nice addition to make the password storage and
> management optional - in complex IdM scenarios, in fact, it might even be a
> business requirement to NOT store passwords in Syncope internal storage.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
