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

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

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

[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)

Reply via email to