-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Update Access Controls reference docs to include cluster_labels #10463
Labels
Comments
pschisa
added
feature-request
Used for new features in Teleport, improvements to current should be #enhancements
ux
c-co
Internal Customer Reference
documentation
and removed
feature-request
Used for new features in Teleport, improvements to current should be #enhancements
c-co
Internal Customer Reference
ux
labels
Feb 18, 2022
Confirmed this is already available using the updates from #4630 as outlined in our trusted cluster docs: https://goteleport.com/docs/setup/admin/trustedclusters/#rbac Only thing missing is to add the |
pschisa
changed the title
Add ability to restrict end user view of trusted clusters in Web UI and tsh
Update Access Controls reference docs to include cluster_labels
Feb 22, 2022
ptgott
added a commit
that referenced
this issue
Sep 9, 2024
Closes #10463 We already mention the `cluster_labels` role field in the role reference, but it could be more explicit that this field deals with Trusted Clusters. This change adds a short table to the role reference to indicate the Teleport resources that correspond to different label fields.
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 10, 2024
Closes #10463 We already mention the `cluster_labels` role field in the role reference, but it could be more explicit that this field deals with Trusted Clusters. This change adds a short table to the role reference to indicate the Teleport resources that correspond to different label fields.
github-actions bot
pushed a commit
that referenced
this issue
Sep 10, 2024
Closes #10463 We already mention the `cluster_labels` role field in the role reference, but it could be more explicit that this field deals with Trusted Clusters. This change adds a short table to the role reference to indicate the Teleport resources that correspond to different label fields.
github-actions bot
pushed a commit
that referenced
this issue
Sep 10, 2024
Closes #10463 We already mention the `cluster_labels` role field in the role reference, but it could be more explicit that this field deals with Trusted Clusters. This change adds a short table to the role reference to indicate the Teleport resources that correspond to different label fields.
github-actions bot
pushed a commit
that referenced
this issue
Sep 10, 2024
Closes #10463 We already mention the `cluster_labels` role field in the role reference, but it could be more explicit that this field deals with Trusted Clusters. This change adds a short table to the role reference to indicate the Teleport resources that correspond to different label fields.
ptgott
added a commit
that referenced
this issue
Sep 11, 2024
Closes #10463 We already mention the `cluster_labels` role field in the role reference, but it could be more explicit that this field deals with Trusted Clusters. This change adds a short table to the role reference to indicate the Teleport resources that correspond to different label fields.
ptgott
added a commit
that referenced
this issue
Sep 11, 2024
Closes #10463 We already mention the `cluster_labels` role field in the role reference, but it could be more explicit that this field deals with Trusted Clusters. This change adds a short table to the role reference to indicate the Teleport resources that correspond to different label fields.
ptgott
added a commit
that referenced
this issue
Sep 11, 2024
Closes #10463 We already mention the `cluster_labels` role field in the role reference, but it could be more explicit that this field deals with Trusted Clusters. This change adds a short table to the role reference to indicate the Teleport resources that correspond to different label fields.
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 11, 2024
Closes #10463 We already mention the `cluster_labels` role field in the role reference, but it could be more explicit that this field deals with Trusted Clusters. This change adds a short table to the role reference to indicate the Teleport resources that correspond to different label fields.
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 11, 2024
Closes #10463 We already mention the `cluster_labels` role field in the role reference, but it could be more explicit that this field deals with Trusted Clusters. This change adds a short table to the role reference to indicate the Teleport resources that correspond to different label fields.
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 11, 2024
Closes #10463 We already mention the `cluster_labels` role field in the role reference, but it could be more explicit that this field deals with Trusted Clusters. This change adds a short table to the role reference to indicate the Teleport resources that correspond to different label fields.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What
Request is to add a mechanism by which a Teleport admin can restrict the end users ability to view specific trusted clusters in the list presented by the Web UI and
tsh clusters
How
Some possible ways I see it being done:
Enable Admins to manually set labels on trusted cluster relationships and then restrict user access to trusted clusters from the root based on those labels and role permissions
Automatically review the resource permissions set by a users role and not present clusters for which they have no resources present
Why
It can be awkward for end users to navigate a large list of trusted clusters, most of which have no resources and show error messages in web UI.
The text was updated successfully, but these errors were encountered: