[
https://issues.apache.org/jira/browse/SYNCOPE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033813#comment-14033813
]
Colm O hEigeartaigh commented on SYNCOPE-505:
---------------------------------------------
I added an initial prototype implementation for DBPasswordPropagationActions.
It checks to see if there is a mandatory missing attribute that corresponds to
password, and then just writes out the password from SyncopeUser "as is" in
this case. What do you think about this approach?
I've tested the prototype + it works. One issue is that it only works if the
Connector uses "CLEARTEXT", as otherwise the supplied password gets hashed.
Should we add another Connector property so that we can tell it to only
hash/encrypt if the supplied password is "plaintext"?
Colm.
> Support propagating non-cleartext passwords to external resources
> -----------------------------------------------------------------
>
> Key: SYNCOPE-505
> URL: https://issues.apache.org/jira/browse/SYNCOPE-505
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Reporter: Francesco Chicchiriccò
> Assignee: Colm O hEigeartaigh
> Fix For: 1.2.0
>
>
> Similarly to SYNCOPE-313 during synchronization, it seems feasible to provide
> some Propagation Actions classes (say {{DBPasswordPropagationActions}} and
> {{LDAPPasswordPropagationActions}} that will propagate non-cleartext password
> values to external resources.
> This might require some changes in the related connector bundles.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
