[
https://issues.apache.org/jira/browse/SYNCOPE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033936#comment-14033936
]
Colm O hEigeartaigh commented on SYNCOPE-505:
---------------------------------------------
{quote}
A special _HASHED_PASSWORD_ boolean attribute - defaults to true when missing -
could be added to the DBTable connector configuration: sounds good.
{quote}
Shouldn't it default to "false" when missing? I.e. "_HASHED_PASSWORD_" being
present and "true" means that the value under _PASSWORD_ should be treated as
hashed + not subsequently hashed with the configured Connector hash algorithm.
Otherwise, the Connector hash algorithm applies.
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)
