| Summary: | REST API - User object should have roles | ||
|---|---|---|---|
| Product: | [Community] Candlepin | Reporter: | Amos Benari <abenari> |
| Component: | candlepin | Assignee: | Bryan Kearney <bkearney> |
| Status: | CLOSED WONTFIX | QA Contact: | John Sefler <jsefler> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 0.5 | CC: | ohadlevy, wpoteat |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-15 19:28:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Amos Benari
2011-09-01 08:59:30 UTC
@Path /users/{uuid}/roles
The User object has a Role set. We don't express it in the JSON because it will introduce an infinite recursion.
As for updating a user by modifying the roles list, it could create a race condition and would not be healthy for the system.
POST roles/{role_id}/users/{username}
DELETE roles/{role_id}/users/{username}
Are used to update the relationships between user and role
1. If a user object will contain the role-ids not role objects it will not recourse. 2. I think updating role by role is acceptable as a work around. However it's not a transactive solution and may produce unexpected results in case of failure. Most users are doing their own authn/authz. Closing until there is a project need. |