Treat users and groups as distinct concepts #489
Merged
Conversation
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
|
+1 |
macintux
added a commit
that referenced
this pull request
Feb 20, 2014
Treat users and groups as distinct concepts
|
Is there a complementary one for basho/riak_ee? |
|
Oh, we should probably do that (or just copy the damn riak-admin script over). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To make it easier to reason about and document the new security behavior, this PR splits roles into users and groups.
Where the code does not or cannot distinguish between users and groups, I continue to refer to roles, but the user interface is constrained to users and groups.
There are 3 projects impacted by this change, all with the same branch name (
jrd-security-role-bifurcation):All should be merged at the same time. I will be filing PRs for each.
/cc @Vagabond