summaryrefslogtreecommitdiff
path: root/docs/content/en/overview/authentication/introduction.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/content/en/overview/authentication/introduction.md')
-rw-r--r--docs/content/en/overview/authentication/introduction.md35
1 files changed, 35 insertions, 0 deletions
diff --git a/docs/content/en/overview/authentication/introduction.md b/docs/content/en/overview/authentication/introduction.md
new file mode 100644
index 000000000..11183c284
--- /dev/null
+++ b/docs/content/en/overview/authentication/introduction.md
@@ -0,0 +1,35 @@
+---
+title: "Authentication"
+description: "An overview of a authentication."
+lead: "An overview of a authentication."
+date: 2022-03-20T12:52:27+11:00
+draft: false
+images: []
+menu:
+ overview:
+ parent: "prologue"
+weight: 210
+toc: false
+aliases:
+ - /docs/features/2fa/
+---
+
+Multi-Factor Authentication or MFA as a concept is separated into three major categories. These categories are:
+
+* something you know
+* something you have
+* something you are
+
+Modern best security practice dictates that using multiple of these categories is necessary for security. Users are
+unreliable and simple usernames and passwords are not sufficient for security.
+
+__Authelia__ enables primarily two-factor authentication. These methods offered come in two forms:
+
+* 1FA or first-factor authentication which is handled by a username and password. This falls into the *something you know*
+ categorization.
+* 2FA or second-factor authentication which is handled by several methods including one-time passwords, authentication
+ keys, etc. This falls into the *something you have* categorization.
+
+In addition to this Authelia can apply authorization policies to individual website resources which restrict which
+identities can access which resources from a given remote address. These policies can require 1FA, 2FA, or outright deny
+access depending on the criteria you configure.