Skip to content

Update docs related to creating bindings to roles #4585

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 16, 2017
Merged

Update docs related to creating bindings to roles #4585

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 2 additions & 9 deletions architecture/additional_concepts/authorization.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -170,15 +170,13 @@ ifdef::openshift-origin,openshift-enterprise,openshift-dedicated[]
|*admin* |A project manager. If used in a
xref:cluster-policy-and-local-policy[local binding], an *admin* user will have
rights to view any resource in the project and modify any resource in the
project except for role creation and quota. If the *cluster-admin* wants to
allow an *admin* to modify roles, the *cluster-admin* must create a
project-scoped `*Policy*` object using JSON.
project except for quota.

|*basic-user* |A user that can get basic information about projects and users.

|*cluster-admin* |A super-user that can perform any action in any project. When
granted to a user within a local policy, they have full control over quota and
roles and every action on every resource in the project.
every action on every resource in the project.

|*cluster-status* |A user that can get basic cluster status information.

Expand Down Expand Up @@ -254,11 +252,6 @@ endif::[]
However, if other default roles are added to users and groups within a local
policy, they become listed in the CLI output, as well.

If you find that these roles do not suit you, a *cluster-admin* user can create
a `*policyBinding*` object named `_<projectname>_:default` with the CLI using a
JSON file. This allows the project *admin* to bind users to roles that are
defined only in the `_<projectname>_` local policy.

[IMPORTANT]
====
The `cluster-` role assigned by the project administrator is limited in a
Expand Down