Skip to content
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.

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

Clarify RBAC rule application #11672

Merged
merged 6 commits into from
Apr 7, 2022
Merged

Conversation

xacrimon
Copy link
Contributor

@xacrimon xacrimon commented Apr 1, 2022

Fixes #11601

@xacrimon xacrimon force-pushed the joel/clarify-rbac-rule-application branch from ba4731b to 869d779 Compare April 1, 2022 16:31
@xacrimon
Copy link
Contributor Author

xacrimon commented Apr 1, 2022

@zmb3 You're too fast:), I reworded it just a second after.

@xacrimon xacrimon requested a review from zmb3 April 1, 2022 16:32
@xacrimon
Copy link
Contributor Author

xacrimon commented Apr 4, 2022

@ptgott Can I get a review?

@@ -76,6 +76,10 @@ spec:
count: 2
```

#### Combining Policies

The authorizer applies require policies within a role together with an OR operator and the sets from each role with an AND operator. In practice, this means that every role with at least one require policy requires one of its policies to be met before a session can be started.
Copy link
Contributor

@ptgott ptgott Apr 4, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • This is the first time we mention the authorizer. Is this the same as the Auth Service? If so, I think we should say "The Auth Service" so readers can better connect this paragraph with their knowledge of Teleport.
  • Is there a term defined earlier in the guide we can use instead of "the sets from each role"? I'm not confident that I understand what this refers to.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. The authorizer usually a common term for some control logic at any point in a stack that decides whether a user has access or not. This isn't a term frequently used in documentation I don't think but I don't have a better name for it since this code can be run at many different places.

  2. Reworded, is it clearer now?

docs/pages/access-controls/guides/moderated-sessions.mdx Outdated Show resolved Hide resolved
@xacrimon xacrimon requested a review from ptgott April 5, 2022 15:20
@xacrimon xacrimon merged commit ad96be2 into master Apr 7, 2022
@xacrimon xacrimon deleted the joel/clarify-rbac-rule-application branch April 7, 2022 14:05
xacrimon added a commit that referenced this pull request Apr 7, 2022
xacrimon added a commit that referenced this pull request Apr 7, 2022
* Write error and return on failed websocket upgrade (#11606)

* Broadcast controls keys if session is moderated (#11661)

* Clarify RBAC rule application (#11672)

* Use a buffered channel for the terminate notifier (#11687)

* Restrict moderated sessions users from accessing V8 kube cluster agents (#11691)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SSH Moderated Sessions will work if only one role matches.
3 participants