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

Posted to dev@syncope.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/08/11 14:08:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16123387#comment-16123387 ] 

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

Commit 81515d7e243e8116409e2be2cb6bf036a305f988 in syncope's branch refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=81515d7 ]

[SYNCOPE-1193] Now read, update and delete works both with key and (user)name for Users, Groups and Any Objects


> 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
>            Assignee: Francesco Chicchiriccò
>             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)