Skip to content

Commit

Permalink
DOCS MFA authentication (#9536)
Browse files Browse the repository at this point in the history
  • Loading branch information
chillu authored Aug 20, 2020
2 parents b810b7d + 72a02a3 commit f8b4570
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions docs/en/02_Developer_Guides/09_Security/03_Authentication.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,18 @@ icon: users-cog
By default, SilverStripe provides a [MemberAuthenticator](api:SilverStripe\Security\MemberAuthenticator\MemberAuthenticator) class which hooks into its own internal
authentication system.

Silverstripe projects created with CMS Recipe 4.7.0 onwards include Multi Factor Authentication (MFA)
through the [silverstripe/mfa](https://github.com/silverstripe/silverstripe-mfa) module.
This increases login security by asking for a code generated on another device,
through TOTP with the [silverstripe/totp-authenticator](https://github.com/silverstripe/silverstripe-totp-authenticator)
module. This step is optional for users, and can be disabled or required by CMS
administrators ([instructions](https://userhelp.silverstripe.org/en/4/optional_features/multi-factor_authentication/)).

To further increase login security, you can install support
for hardware tokens through the [silverstripe/webauthn-authenticator](https://github.com/silverstripe/silverstripe-webauthn-authenticator)
module. These tokens virtually eliminiate the risk of [credential phishing](https://en.wikipedia.org/wiki/Phishing),
but also require a bit of care during setup.

## User Interface

SilverStripe comes with a default login form interface,
Expand Down

0 comments on commit f8b4570

Please sign in to comment.