Common end-user access request actions #11594
WilliamLoy
started this conversation in
General
Replies: 1 comment
-
Also, to get a list of available roles, you can run:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When a user needs to request access to resources, they can do so by utilizing the Teleport Access Request features. This document discusses some common actions that an end-user may need to request access successfully.
Requesting a role from command line
Users can request a role using the following
tsh
command:tsh login --proxy=teleport-cluster --request-roles=k3-role
The user should receive the following output:
The user remains on the
Waiting for request approval...
line until the request is approved. When the request is approved, the user is logged in with the approved role attached to the session. This can be verified withtsh status
To request access without waiting the user can add the
--request-nowait
flag. With the no-wait flag, the user can check for request approval later.Listing role requests
To login as an approved role, the user must have the approved
request-id
. A user can list their access requests by using the following command:tsh request ls
When they have located the
request-id
they can log in with the approved role attached to the session using the following command:tsh login --request-id=<request-id>
Adding a reason to a request
Users might be required to add a reason when requesting role access. They can add a reason to their request by using the following command:
tsh login --proxy=teleport-cluster --request-roles=k3-role --request-reason="need k3 access"
Requesting a role from the web interface
From here, you can choose to go back to your request list or make another request.
Beta Was this translation helpful? Give feedback.
All reactions