Odoo Community Association

Enforce Two-Factor Authentication

Beta License: AGPL-3 OCA/server-auth Translate me on Weblate Try me on Runboat

This module forces internal users to configure two-factor authentication (a TOTP authenticator app) before they log in.

Enforcement works like the password expiry flow of password_security: nobody is logged out when the module is installed, but on their next login users are held in a mandatory step and cannot reach the backend until they have enabled an authenticator app.

Members of the Exempt from 2FA enforcement group are never forced. Portal and public users are out of scope at the moment.

Table of contents

Usage

Once installed, any enforced internal user without an authenticator app configured will, on their next login:

  1. Enter their login and password as usual.
  2. Be redirected to a mandatory setup page showing a QR code and secret key.
  3. Scan the code with an authenticator app and enter the generated code.
  4. Be handed over to the standard two-factor step to complete the login.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • ForgeFlow

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/server-auth project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.