Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Document second_factor behavior for v16+ #48767

Open
ptgott opened this issue Nov 11, 2024 · 0 comments · May be fixed by #52392
Open

Document second_factor behavior for v16+ #48767

ptgott opened this issue Nov 11, 2024 · 0 comments · May be fixed by #52392

Comments

@ptgott
Copy link
Contributor

ptgott commented Nov 11, 2024

Applies To

  • docs/pages/admin-guides/management/security/reduce-blast-radius.mdx
  • docs/pages/includes/config-reference/auth-service.yaml
  • docs/pages/reference/access-controls/authentication.mdx

Any other mentions of the auth_service.authentication.second_factor configuration field.

Details

As of v16.0.0, the auth_service.authentication.second_factor behavior changed so that:

Support for disabling multi-factor authentication has been removed. Teleport
will refuse to start until the second_factor setting is set to on, webauthn
or otp.

This change only affects self-hosted Teleport users, as Teleport Enterprise (Cloud) has
always required multi-factor authentication.

(Changelog)

How will we know this is resolved?

All mentions of the second_factor field describe the v16+ behavior.

Related Issues

ptgott added a commit that referenced this issue Feb 21, 2025
Closes #48767

Remove the section re: making MFA mandatory, since in v16 and after, it
is always mandatory. This removes the last mention in the docs of the
pre-v16 `second_factor` behavior.
@ptgott ptgott linked a pull request Feb 21, 2025 that will close this issue
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant