Enable 2FA authentication with TOTP

Installs: 11 848

Dependents: 0

Suggesters: 0

Security: 0

Stars: 5

Watchers: 3

Forks: 2

Open Issues: 13


0.0.2 2018-02-16 02:47 UTC

This package is auto-updated.

Last update: 2024-04-27 15:37:10 UTC


Code Coverage Scrutinizer Code Quality

SilverStripe TOTP (Time-based One Time Password) Authenticator

This is a time-based token authenticator for SilverStripe. It allows users with apps such as Google Authenticator or Authy to generate a code to be used for logging into a SilverStripe installation. Backup codes are also available to the user, in case their second factor is lost, stolen, or otherwise unavailable.

This extends and builds from Firesphere's MFABootstrap module, and has been tested with a vanilla installation of CWP 2.0 and SilverStripe 4.1.1

Supported Authenticators

It is difficult to support an exhaustive list of authenticator apps, but for the purposes of an initial release the following authenticators are supported.

  • Google Authenticator
  • Authy

If you know of any others that can be added to this list, raise a pull request along with any code and unit tests you've added to ensure support.


composer require elliot-sawyer/totp-authenticator


Add the following to config.yml

    - ElliotSawyer\TOTPAuthenticator\MemberExtension

        totpauthenticator: %$ElliotSawyer\TOTPAuthenticator\TOTPAuthenticator


Google Authenticator and Authy only support tokens generated with SHA-1. Other authenticators MAY implement SHA-256 or SHA-512 as outlined in RFC6238. You may use the Config API to adjust this algorithm if you need to support a specific TOTP authenticator

  algorithm: 'sha512'


  1. Login to CMS as usual, taking care to use the "default" authenticator. Visit the Security admin and select your user. Ignore the TOTPSecret field for now. Tick the "MFA Enabled" and “Reset MFA codes” and save the Member.
  2. Take note of your backup tokens, as they can be used to log into your account if the authenticator is lost, stolen, or otherwise unavailable. These are stored encrypted in the database and are not recoverable. They must be reset if lost.
  3. Return to Main tab and reveal the “Second Factor Token Secret. Scan the QR code with Google Authenticator or Authy. Your website name ( as defined by Site title) and your username are visible at the end of Google Authenticator.
  4. Visit https://yoursite.local/Security/login/totpauthenticator to log in. You will be prompted for your second factor access code.


Please raise issues and feature requests at https://github.com/elliot-sawyer/totp-authenticator/issues