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

[v14] docs: describe local user storage and password hashing #45998

Merged
merged 1 commit into from
Aug 29, 2024
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
7 changes: 4 additions & 3 deletions docs/pages/management/admin/users.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,9 @@ description: Learn how to manage local users in Teleport. Local users are stored
---

In Teleport, **local users** are users managed directly via Teleport, rather
than a third-party identity provider.
than a third-party identity provider. All local users are stored in Teleport's
cluster state backend, which contains the user's name, their roles and traits,
and a bcrypt password hash.

This guide shows you how to:

Expand Down Expand Up @@ -61,7 +63,7 @@ The user completes registration by visiting this URL in their web browser,
picking a password, and configuring multi-factor authentication. If the
credentials are correct, the Teleport Auth Server generates and signs a new
certificate, and the client stores this key and will use it for subsequent
logins.
logins.

The key will automatically expire after 12 hours by default, after which
the user will need to log back in with their credentials. This TTL can be
Expand Down Expand Up @@ -137,4 +139,3 @@ information, see [GitHub SSO](../../access-controls/sso/github-sso.mdx).

</TabItem>
</Tabs>

Loading