This release is a pre-release and may not be stable for production use.
Auth Oauth Environment
This module extends the functionality of server environment to support OAuth providers, and allows you to enable providers and set client_id key according to environment. (Refer to module server_environment for more informations)
Installation
To install this module, you need to have the server_environment module installed and properly configured.
Configuration
To configure this module, you need to add a section [auth_oauth.provider_simple_name] to you server_environment_files configurations, where ‘provider_simple_name’ match the simplified name field on auth.oauth.provider.
‘provider_simple_name’ is the first part (until first space character) in lower case of provider name. Using existing providers, it could be either google, odoo.com, or facebook.
For example, if you want to activate Google and Odoo.com, your server_environment_files should look like this
[auth_oauth.google] enabled=True client_id=123456789101-abcdefghijklmnopqrstuvwxyz000000 [auth_oauth.odoo.com] enabled=True
Any provider not being enabled through server_environment_files will be set as disabled automatically.
If you want to define a new custom provider, you should pay attention to the name to use in the server_environment_files. If you create a provider with ‘Dummy auth provider’ as its name, then the section should be named [auth_oauth.dummy].
Usage
Once configured, Odoo will read from server_environment_files the following fields of auth.oauth.provider :
Allowed (enabled)
Client ID (client_id)
Known issues / Roadmap
Due to the specific nature of this module, it cannot be tested on OCA runbot.
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 smash it by providing detailed and welcomed feedback.
Credits
Images
Odoo Community Association: Icon.
Contributors
Akim Juillerat <akim.juillerat@camptocamp.com>
Do not contact contributors directly about support or help with technical issues.
Maintainer
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.
To contribute to this module, please visit https://odoo-community.org.
Metadata
Release files for odoo11-addon-auth-oauth-environment 11.0.1.0.0.99.dev3
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 |
|---|---|---|---|---|
| odoo11_addon_auth_oauth_environment-11.0.1.0.0.99.dev3-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for odoo11_addon_auth_oauth_environment-11.0.1.0.0.99.dev3-py2.py3-none-any.whl |
Release files / odoo11_addon_auth_oauth_environment-11.0.1.0.0.99.dev3-py2.py3-none-any.whl
| Download URL | odoo11_addon_auth_oauth_environment-11.0.1.0.0.99.dev3-py2.py3-none-any.whl |
|---|---|
| Size | 17.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
cc6849cb396b6be59258ba03256cbcecf7fe4e78a8589432990e06e6f83e2c6d
|
|
BLAKE2b-256 checksum How to use checksums |
845274a8fd314766676bbe26977bd9e2b5644e24b288a6214968ed9a2e6f07a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo11-addon-auth-oauth-environment 11.0.1.0.0.99.dev3
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.