forked from go-gitea/gitea
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'giteaofficial/main'
* giteaofficial/main: Fix counting and filtering on the dashboard page for issues (go-gitea#26657) add mfa doc (go-gitea#26654) [Refactor] getIssueStatsChunk to move inner function into own one (go-gitea#26671) Use line-height: normal by default (go-gitea#26635) Improve repo sub menu (go-gitea#26531) Fix organization list in dashboard (go-gitea#26650)
- Loading branch information
Showing
11 changed files
with
284 additions
and
171 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
--- | ||
date: "2023-08-22T14:21:00+08:00" | ||
title: "Usage: Multi-factor Authentication (MFA)" | ||
slug: "multi-factor-authentication" | ||
weight: 15 | ||
toc: false | ||
draft: false | ||
menu: | ||
sidebar: | ||
parent: "usage" | ||
name: "Multi-factor Authentication (MFA)" | ||
weight: 15 | ||
identifier: "multi-factor-authentication" | ||
--- | ||
|
||
# Multi-factor Authentication (MFA) | ||
|
||
Multi-factor Authentication (also referred to as MFA or 2FA) enhances security by requiring a time-sensitive set of credentials in addition to a password. | ||
If a password were later to be compromised, logging into Gitea will not be possible without the additional credentials and the account would remain secure. | ||
Gitea supports both TOTP (Time-based One-Time Password) tokens and FIDO-based hardware keys using the Webauthn API. | ||
|
||
MFA can be configured within the "Security" tab of the user settings page. | ||
|
||
## MFA Considerations | ||
|
||
Enabling MFA on a user does affect how the Git HTTP protocol can be used with the Git CLI. | ||
This interface does not support MFA, and trying to use a password normally will no longer be possible whilst MFA is enabled. | ||
If SSH is not an option for Git operations, an access token can be generated within the "Applications" tab of the user settings page. | ||
This access token can be used as if it were a password in order to allow the Git CLI to function over HTTP. | ||
|
||
> **Warning** - By its very nature, an access token sidesteps the security benefits of MFA. | ||
> It must be kept secure and should only be used as a last resort. | ||
The Gitea API supports providing the relevant TOTP password in the `X-Gitea-OTP` header, as described in [API Usage](development/api-usage.md). | ||
This should be used instead of an access token where possible. |
This file contains 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 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 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 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.