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

[v8] backport #9866 (docs update for access request locks) #9983

Merged
merged 2 commits into from
Jan 28, 2022
Merged
Changes from all commits
Commits
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
8 changes: 8 additions & 0 deletions docs/pages/access-controls/guides/locking.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,7 @@ A lock can target the following objects or attributes:
- a Teleport node by the node's UUID (effectively unregistering it from the
cluster)
- a Windows desktop by the desktop's name
- an [access request](../../enterprise/workflow/index.mdx) by UUID

## Prerequisites

Expand Down Expand Up @@ -79,6 +80,13 @@ To create a new lock, one can run the `tctl lock` command:
# Created a lock with name "dc7cee9d-fe5e-4534-a90d-db770f0234a1".
```
</TabItem>
<TabItem label="Access request">
All connections using elevated privileges from the matching access request will be locked.
```code
$ tctl lock --access-request=261e80c5-357b-4c43-9b67-40a6bc4c6e4d --ttl=24h
# Created a lock with name "dc7cee9d-fe5e-4534-a90d-db770f0234a1".
```
</TabItem>
</Tabs>

<Details
Expand Down