-
Notifications
You must be signed in to change notification settings - Fork 210
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[SPOOL-197] [#111] clients can be added to ACL even if user exist
This addresses three long-standing issues: 1. when a user exists in the Chef Server, it was not possible to add a client to an object's ACL if that client had the same name. The logic that retrieved actors based on names obeyed org constraints for clients, but looked at the global users list without consideration for whether or not the users were members of the organization. This has been corrected, so that the presence of a user anywhere in the system can no longer block a same-named client from being added to an object's ACL. 2. when an actor being added does not exist or is not in the organization, the request would fail with a 400 'missing/invalid actor' message. It would not give any indication of which actor(s) caused a problem. This has been corrected, and the error message now includes the list of actor(s) that could not be added. 3. when an actor being added exists as both an org client and a user, the same "400 missing/invalid actor" message would be sent. Occurrences of this will be reduced now that we restrict the search to users in the org, but can still occur if an org-user shares a name with a client. We have changed this to reply with "422 (Unprocessable Entity)". The error message explains that the actor name(s) are ambiguous and provides the list of names. Further updates will provide a means to The next round of updates will expand the acl API to accept and provide `clients` and `users` attributes. Using those attributes instead of `actors` when updating ACLs will give a workaround for the scenario described above (3) and will be the preferred method for updating ACLs via the API.
- Loading branch information
Marc Paradise
committed
Aug 18, 2016
1 parent
683cf38
commit dc5526b
Showing
7 changed files
with
155 additions
and
29 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters