From 72a02a3d0e784b87ea95bcf8d4795023d43cdc08 Mon Sep 17 00:00:00 2001 From: Ingo Schommer Date: Thu, 20 Aug 2020 18:32:57 +1200 Subject: [PATCH] Update docs/en/02_Developer_Guides/09_Security/03_Authentication.md Co-authored-by: Serge Latyntsev --- docs/en/02_Developer_Guides/09_Security/03_Authentication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/02_Developer_Guides/09_Security/03_Authentication.md b/docs/en/02_Developer_Guides/09_Security/03_Authentication.md index d46ad9437..ad5184187 100644 --- a/docs/en/02_Developer_Guides/09_Security/03_Authentication.md +++ b/docs/en/02_Developer_Guides/09_Security/03_Authentication.md @@ -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 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) 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.