-
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
Stable UNIX users: docs #51662
Stable UNIX users: docs #51662
Conversation
@@ -218,6 +218,39 @@ If multiple entries are specified in the `host_user_uid` or `host_user_gid` only | |||
|
|||
</Admonition> | |||
|
|||
For Teleport users that don't have a `host_user_uid` trait, starting from Teleport 17.3, it's possible to configure the cluster to assign the same UID for any given username for automatically created host users across all Teleport SSH instances. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we mention version numbers from previous major versions? If we do, should we get rid of the version numbers once we're past the version compatibility window? In this case we could safely get rid of the numbers in the v19 docs, for example.
Amplify deployment status
|
docs/pages/enroll-resources/server-access/guides/host-user-creation.mdx
Outdated
Show resolved
Hide resolved
@espadolini See the table below for backport results.
|
Docs for #50292, implemented in #51102 and #51200
Related RFD: #50414