You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "Marco Di Sabatino Di Diodoro (JIRA)" <ji...@apache.org> on 2017/08/10 13:25:00 UTC

[jira] [Updated] (SYNCOPE-1193) Add the option to update a user via REST by using the username as key

     [ https://issues.apache.org/jira/browse/SYNCOPE-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marco Di Sabatino Di Diodoro updated SYNCOPE-1193:
--------------------------------------------------
    Summary: Add the option to update a user via REST by using the username as key  (was: Add the option to edit a user via REST by using the username as key)

> Add the option to update a user via REST by using the username as key
> ---------------------------------------------------------------------
>
>                 Key: SYNCOPE-1193
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1193
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.4
>            Reporter: Marco Di Sabatino Di Diodoro
>             Fix For: 2.0.5, 2.1.0
>
>
> During an update via REST, you must use key to upgrade the user. This happens because during the search of the last etag, the core uses userDAO.findLastChange(key). If you set the username it returns a NotFoundException.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)