-
Notifications
You must be signed in to change notification settings - Fork 2k
MWI: Add lock targets for join token name and bot instance ID #56021
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
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
1b34407
MWI: Add lock targets for join token name and bot instance ID
timothyb89 b5160d6
Set join token cert request field for non-renewable bot identities
timothyb89 8b81764
Fix ASN ID and pass through join token name in impersonated certs
timothyb89 a781439
Tweak docstrings and add missing references for lib/decision
timothyb89 cf7d19e
Clarify docstrings
timothyb89 856a84f
Merge remote-tracking branch 'origin/master' into timothyb89/bound-ke…
timothyb89 ff02725
Fix failing tests
timothyb89 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
30 changes: 27 additions & 3 deletions
30
api/gen/proto/go/teleport/decision/v1alpha1/ssh_access.pb.go
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
20 changes: 16 additions & 4 deletions
20
api/gen/proto/go/teleport/decision/v1alpha1/ssh_identity.pb.go
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
19 changes: 16 additions & 3 deletions
19
api/gen/proto/go/teleport/decision/v1alpha1/tls_identity.pb.go
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
If
bot_instance_idandjoin_tokencan only exist together, should they be combined in a separate message?What happens to the
userfield in case of a bot instance - is this worth a comment?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.
It's a bit messy but it probably doesn't make sense to move these fields into a separate message.
Bots are a variant of users and have a username (
bot-foo, generally), souserwill be set for both human users and bots. All bots have abot_instance_id, but only some bots will have ajoin_tokenset. The fields will be empty for regular users, which is a convention shared with other fields, e.g.server_idis only set for servers,mfa_deviceis only set when a user has an MFA device, etc.