-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
DOCS Added user guide and screenshots
- Loading branch information
1 parent
2b0b337
commit 4be6f2e
Showing
6 changed files
with
46 additions
and
7 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
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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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,27 @@ | ||
# User guide | ||
|
||
## Setting up a user with two factor authentication | ||
Setting up two factor authentication can only be performed by a CMS user with permissions to the Security section of your SilverStripe CMS. | ||
|
||
1. Log into the CMS. | ||
2. For a given user select, "Enable Two Factor Authentication" checkbox and save the user. This will generate a Timed One-Time Password token and a QR code to set up in your second factor application (Google Authenticator for example). | ||
|
||
![2FA token and QR code](_images/2fa-token-qr.png) | ||
|
||
4. Scan QR (or enter the token) into your two factor authentication application and use alongside your regular email and password when logging into the CMS. | ||
|
||
![Security token prompt](_images/2fa-login.png) | ||
|
||
## Setting backup tokens | ||
You can set up backup security tokens just in case you lose access to your second factor device. | ||
|
||
1. Log into the CMS (again you will need access to the Security section). | ||
2. For a given user, select the "Backup Tokens" tab. | ||
3. Click "Add OTP Backup Token" | ||
|
||
![Backup tokens](_images/2fa-backup.png) | ||
|
||
4. Enter a random set of characters to act as the backup token (this is up to you to provide a suitable token). Save. | ||
5. You can now use this token in place of two factor authentication. | ||
|
||
Tokens are single use by default and will be removed from the pool of backup tokens for a given user once entered during the log in process. This can be configured to be multiuse by a developer in the [configuration](configuration.md) by setting `single_use: false`. This is not recomendaed as it negates the improved security of having a second factor involved in your log in process. Effectively you end up with two passwords with this configuration setting, and is only marginally better security wise. |