Handle the login field from the JWT token in OAuth signup. This is useful when you need to create users where the login field is different from the email field.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0When users sign up or log in through an OAuth provider, this module uses the login value returned by the provider instead of the email address, so accounts can have a login that differs from the email.
This module changes how Odoo builds the values used to create a user account during OAuth signup.
When someone signs in with an external OAuth provider, Odoo normally prepares the new user's data from the information returned by the provider. With this module installed, if the provider's response includes a login value, that value is used as the user's login instead of the default one.
- It only affects the OAuth signup flow handled by the
res.usersmodel. - It does not add any new screen, menu, button or report.
- It does not add any configuration option; it works automatically once installed.
- It relies on the standard OAuth authentication feature (
auth_oauth).
This is useful when the external identity provider returns a username or identifier that should be the Odoo login, while the email address is different. No other business rules, checks or scheduled actions are added by the code.
Depends on
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/server-auth.
terminal Installation and usage
OCA documentation · Odoo 18.0Usage
Source · Odoo 18.0If a login field is present in the token, it will be used as login field on user signup. When using the auth_oidc module, the Token Map can be populated like this, for instance: preferred_username:login.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.