syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SYNCOPE-946) Encrypted attribute values not managed as password values
Date Mon, 03 Oct 2016 12:25:20 GMT

    [ https://issues.apache.org/jira/browse/SYNCOPE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542304#comment-15542304
] 

ASF subversion and git services commented on SYNCOPE-946:
---------------------------------------------------------

Commit 97bdc56760b6f3219e27268a992f533689fd881e in syncope's branch refs/heads/2_0_X from
[~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=97bdc56 ]

[SYNCOPE-946] i18n handling of confirmation message


> Encrypted attribute values not managed as password values
> ---------------------------------------------------------
>
>                 Key: SYNCOPE-946
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-946
>             Project: Syncope
>          Issue Type: Bug
>          Components: console, enduser
>    Affects Versions: 2.0.0
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>             Fix For: 2.0.1, 2.1.0
>
>
> When editing an user / group / any object with an encrypted attribute, the value is treated
as plain text.
> How to reproduce:
>  # create an Encrypted schema {{sharedPassword}}
>  # create an user, and set the {{secret}} value for {{sharedPassword}}
>  # edit such user from the admin console: the value for {{sharedPassword}} will be the
encrypted string
> As a result, when clicking on Finish, the encrypted value will be sent again to the core,
which will then encrypt it again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message