Skip to Content
Odoo model

auth.totp.rate.limit.log

TOTP rate limit logs. Defined in module auth_totp; exists in Odoo 16, 17, 18, 19, 20. Across the upgrade steps we tracked: 0 fields added, 1 removed, 0 renamed.

  1. Odoo 16 auth_totp_mail_enforce
  2. Odoo 17 auth_totp_mail_enforce
  3. Odoo 18 auth_totp_mail_enforce
  4. Odoo 19 auth_totp
  5. Odoo 20 auth_totp

Odoo 16 to 17

Community only All changes in this step

No change to this model's own fields in this step.

Odoo 17 to 18

Community only All changes in this step

No change to this model's own fields in this step.

Odoo 18 to 19

Community + Enterprise All changes in this step

Fields removed (1)

FieldTypeModuleNotes
scopecharauth_totp_mail_enforceIts module (auth_totp_mail_enforce) is not in Odoo 19: removed, renamed or merged into another module.

Odoo 19 to 20

Community + Enterprise All changes in this step

No change to this model's own fields in this step.

All fields declared on auth.totp.rate.limit.log (4)

Fields this model declares itself in any version, with the versions they exist in. Inherited fields (mail.thread and other mixins) are on the parent model's page.

present not present not covered (Enterprise, Odoo 16 and 17)

Show all 4 fields
FieldTypeLabelModule1617181920
ipcharauth_totp
limit_typeselectionauth_totp
scopecharauth_totp_mail_enforce
user_idmany2one res.usersauth_totp

Related models

Linked by its relational fields: res.users

Coverage. Odoo 16 to 17 and 17 to 18 compare Community modules only (the Enterprise 16 and 17 sources are not available to us). Odoo 18 to 19 and 19 to 20 include Community and Enterprise modules. Everything here comes from a static read of the Odoo source code: a field counts as removed only when no parent model, mixin or delegated model still provides it. Fields created dynamically at run time can be missed, and entries we could not confirm are marked as low confidence.