-
-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[18.0][MIG] auth_api_key: Migration to 18.0 #701
Conversation
…custom one from shopinvader
Get rid of keychain dependency
Co-Authored-By: qgroulard <[email protected]>
Api key is now based on the new version of server env Key belong to a specifiv database that can be requested based on the domain name. Just setup the db_filter with "%d^" to filter based on domain name
… to manage auth api keys
Add a migration script to create the auth.api.key records from keys defined into the cfg file Provides a specific serction name builder to continue reading the key info from the same section as the one expected by the previous version
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: server-auth-17.0/server-auth-17.0-auth_api_key Translate-URL: https://translation.odoo-community.org/projects/server-auth-17-0/server-auth-17-0-auth_api_key/
Currently translated at 100.0% (17 of 17 strings) Translation: server-auth-17.0/server-auth-17.0-auth_api_key Translate-URL: https://translation.odoo-community.org/projects/server-auth-17-0/server-auth-17-0-auth_api_key/it/
Currently translated at 100.0% (17 of 17 strings) Translation: server-auth-17.0/server-auth-17.0-auth_api_key Translate-URL: https://translation.odoo-community.org/projects/server-auth-17-0/server-auth-17-0-auth_api_key/it/
An archived user should not have an active api key anymore. But to stay backward compatible the migration script will keep all key active.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thienvh332 LG but please report the rationale to keep this module as is in the description of the module, thanks :)
(in separate commmit that we can backport)
/ocabot migration auth_api_key |
6327e96
to
10a5106
Compare
@thienvh332 would you mind backporting the readme update to v17? /ocabot merge nobump |
What a great day to merge this nice PR. Let's do it! |
Congratulations, your PR was merged at 26ac77c. Thanks a lot for contributing to OCA. ❤️ |
|
OCA - Port:
Summary:
This PR migrates the
auth_api_key
module to Odoo 18.0.Background:
Since Odoo 14.0, native API keys (
res.users.apikey
) have been supported, allowing users to authenticate XMLRPC/JSONRPC calls using their API key instead of a password. In Odoo 18.0, the native API key feature has been enhanced.Some special features of the module:
auth="bearer"
)Why keep
auth_api_key
:The
auth_api_key
module, introduced in Odoo 10.0, offers unique advantages over native API keys.Some special features of the module:
e.g., for system users in a shopinvader case
).Given these advantages, particularly in use case like system user authentication, we have decided to retain and migrate the
auth_api_key
module to Odoo 18.0.