Update docs/en/02_Developer_Guides/09_Security/03_Authentication.md

Co-authored-by: Serge Latyntsev <dnsl48@gmail.com>
This commit is contained in:
Ingo Schommer 2020-08-20 18:32:57 +12:00 committed by GitHub
parent c54f8e4864
commit 72a02a3d0e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -16,7 +16,7 @@ through TOTP with the [silverstripe/totp-authenticator](https://github.com/silve
module. This step is optional for users, and can be disabled or required by CMS 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/)). administrators ([instructions](https://userhelp.silverstripe.org/en/4/optional_features/multi-factor_authentication/)).
To further increase login security, you can opt to install support To further increase login security, you can install support
for hardware tokens through the [silverstripe/webauthn-authenticator](https://github.com/silverstripe/silverstripe-webauthn-authenticator) 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), 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. but also require a bit of care during setup.