Roles/user groups #1321
Closed
Roles/user groups #1321
Milestone
Comments
related to #951 and graylog-labs/graylog2-web-interface#629 |
kroepke
added a commit
that referenced
this issue
Jul 24, 2015
- add /system/ldap/settings/groups endpoints for managing the mapping - correctly resolve a user's roles to permissions when retrieving the user (so that the web interface gets the correct set of permissions) - some cleanup regarding bindings - add new permissions for reading/editing ldap group mappings, which can be done independently of configuring ldap system settings - group mapping uses the objectid of roles, not their names, so they work correct after role renames issue #1321 #951
kroepke
added a commit
that referenced
this issue
Aug 4, 2015
kroepke
added a commit
that referenced
this issue
Aug 5, 2015
kroepke
added a commit
that referenced
this issue
Aug 10, 2015
ensure the Reader and Admin roles are always present during start - reader role does not contain the user-specific permissions needed to edit and change the password of the current user, these need to be set during user creation in that entity - admin is simply "*" both built-in roles cannot be edited/deleted or otherwise changed. fixes missing description when creating a role issue #1321 #951
This was referenced Aug 11, 2015
Closed
Closing this because it's done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to support a more usable permission model we need to implement roles to group permissions and assign them to users.
The text was updated successfully, but these errors were encountered: