[
https://issues.apache.org/jira/browse/SYNCOPE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-426:
-------------------------------------------
Description:
As recently reported in mailing list [1], updating an user requires to pass its
id both as path parameter and embedded in the provided UserMod.
While having both parameters (id and UserMod) seems to be unavoidable to adhere
to REST best practices, it would be quite easy to allow an empty id in UserMod.
Same applies to role update and RoleMod.
[1] http://markmail.org/message/zgh27isscw3hvwfx
was:
As recently reported in mailing list [1], updating an user requires to pass its
id both as path parameter and embedded in the provided UserMod.
While having both parameters (id and UserMod) seems to be unavoidable to adhere
to REST best practices, it would be quite easy to allow an empty id in UserMod.
Same applies for role update and RoleMod.
[1] http://markmail.org/message/zgh27isscw3hvwfx
Labels: rest (was: )
> UserService#update and RoleService#update require entity id to be specified
> twice
> ---------------------------------------------------------------------------------
>
> Key: SYNCOPE-426
> URL: https://issues.apache.org/jira/browse/SYNCOPE-426
> Project: Syncope
> Issue Type: Bug
> Affects Versions: 1.1.4
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Priority: Minor
> Labels: rest
> Fix For: 1.1.5, 1.2.0
>
>
> As recently reported in mailing list [1], updating an user requires to pass
> its id both as path parameter and embedded in the provided UserMod.
> While having both parameters (id and UserMod) seems to be unavoidable to
> adhere to REST best practices, it would be quite easy to allow an empty id in
> UserMod.
> Same applies to role update and RoleMod.
> [1] http://markmail.org/message/zgh27isscw3hvwfx
--
This message was sent by Atlassian JIRA
(v6.1#6144)
