Skip to content
This repository was archived by the owner on Feb 8, 2024. It is now read-only.

[v11] Handle private key policy errors and config (#1298)#1311

Merged
kimlisa merged 3 commits intoteleport-v11from
lisa/v11/backport-private-key-error-handling
Nov 1, 2022
Merged

[v11] Handle private key policy errors and config (#1298)#1311
kimlisa merged 3 commits intoteleport-v11from
lisa/v11/backport-private-key-error-handling

Conversation

@kimlisa
Copy link
Copy Markdown
Contributor

@kimlisa kimlisa commented Oct 28, 2022

backport of #1298 to teleport-v11

Requires

There are three ways we determine if use of private key is enabled:

-Cluster config: this setting won't render the login form,
it will just direct user to login with other supported methods
- 'privateKeyPolicyEnabled' flag: only returned with a 200 for resets
and invites. This flag was required so that we can additionally render
recovery codes if any (only for Teleport Cloud)
- Checking if the error returned contains the backend hard coded
keywords ('hardware_key' or 'hardware_key_touch'). Role configs
will require an attempt (either logging in or assuming an access request)
before the backend checks if this user requires use of private keys.
@kimlisa kimlisa changed the title Handle private key policy errors and config (#1298) [v11] Handle private key policy errors and config (#1298) Oct 28, 2022
@kimlisa kimlisa enabled auto-merge (squash) November 1, 2022 17:52
@kimlisa kimlisa merged commit 0ebff10 into teleport-v11 Nov 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants