]> source.dussan.org Git - gitea.git/commit
add mfa doc (#26654) (#26674)
authorGiteabot <teabot@gitea.io>
Wed, 23 Aug 2023 01:57:01 +0000 (09:57 +0800)
committerGitHub <noreply@github.com>
Wed, 23 Aug 2023 01:57:01 +0000 (01:57 +0000)
commit2f4de240c1c53fe38f4fc167931362deff0f3833
tree6685abb395491ab81d88540af372c6872b159c9e
parente1fa3d1d696db9f9b48f38254ea61d230f5eefe5
add mfa doc (#26654) (#26674)

Backport #26654 by @lunny

copy and modified from #14572

> Whilst debating enforcing MFA within our team, I realised there isn't
a lot of context to the side effects of enabling it. Most of us use Git
over HTTP and would need to add a token.

I plan to add another PR that adds a sentence to the UI about needing to
generate a token when enabling MFA if HTTP is to be used.

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: techknowlogick <techknowlogick@gitea.io>
Co-authored-by: silverwind <me@silverwind.io>
docs/content/usage/multi-factor-authentication.en-us.md [new file with mode: 0644]