[
https://issues.apache.org/jira/browse/SYNCOPE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033931#comment-14033931
]
Francesco Chicchiriccò commented on SYNCOPE-505:
------------------------------------------------
{quote}
Could we have a new (boolean) attribute __HASHED_PASSWORD__ or something?
Alternatively, we could use a predefined prefix/suffix on the __PASSWORD__. Any
preferences?
{quote}
A special {{__HASHED_PASSWORD__}} boolean attribute - defaults to {{true}} when
missing - could be added to the DBTable connector configuration: sounds good.
We need to open an issue on [ConnId's
JIRA|https://connid.atlassian.net/browse/DB] then, targeted to DBTable
connector 2.1.7.
{quote}
One query would be whether we should also follow this logic if the DB Connector
has a CLEARTEXT value? I think we should, but want to verify it.
{quote}
Agree.
> 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)
