Enforce Two-Factor Authentication
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:
Enter their login and password as usual.
Be redirected to a mandatory setup page showing a QR code and secret key.
Scan the code with an authenticator app and enter the generated code.
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
Contributors
ForgeFlow S.L. <contact@forgeflow.com>
Laura Cazorla <laura.cazorla@forgeflow.com>
Maintainers
This module is maintained by the OCA.
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.
Metadata
Release files for odoo-addon-auth-totp-enforce 18.0.1.0.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_auth_totp_enforce-18.0.1.0.0.5-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_auth_totp_enforce-18.0.1.0.0.5-py3-none-any.whl |
Release files / odoo_addon_auth_totp_enforce-18.0.1.0.0.5-py3-none-any.whl
| Download URL | odoo_addon_auth_totp_enforce-18.0.1.0.0.5-py3-none-any.whl |
|---|---|
| Size | 31.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
51f41dae7a494b71c6735f4d383429010eb21097cc5301f6413997b823df5365
|
|
BLAKE2b-256 checksum How to use checksums |
ee9596e183346c628dcd93c0d3a90b9ad8de9665de930b6a452c6cb9a69a26fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-auth-totp-enforce 18.0.1.0.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
