diff --git a/README.md b/README.md index c266459887..d3e9afc194 100644 --- a/README.md +++ b/README.md @@ -26,7 +26,7 @@ addon | version | maintainers | summary [auth_api_key_server_env](auth_api_key_server_env/) | 15.0.1.0.0 | | Configure api keys via server env. This can be very useful to avoid mixing your keys between your various environments when restoring databases. All you have to do is to add a new section to your configuration file according to the following convention: [auth_ldaps](auth_ldaps/) | 15.0.1.0.0 | | Allows to use LDAP over SSL authentication [auth_oauth_multi_token](auth_oauth_multi_token/) | 15.0.1.0.0 | | Allow multiple connection with the same OAuth account -[auth_oidc](auth_oidc/) | 15.0.1.0.0 | [![sbidoul](https://github.com/sbidoul.png?size=30px)](https://github.com/sbidoul) | Allow users to login through OpenID Connect Provider +[auth_oidc](auth_oidc/) | 15.0.1.0.1 | [![sbidoul](https://github.com/sbidoul.png?size=30px)](https://github.com/sbidoul) | Allow users to login through OpenID Connect Provider [auth_saml](auth_saml/) | 15.0.1.1.1 | | SAML2 Authentication [auth_session_timeout](auth_session_timeout/) | 15.0.1.0.0 | | This module disable all inactive sessions since a given delay [auth_signup_verify_email](auth_signup_verify_email/) | 15.0.1.0.0 | | Force uninvited users to use a good email for signup diff --git a/auth_oidc/README.rst b/auth_oidc/README.rst index 3c6265151c..5df7141bcd 100644 --- a/auth_oidc/README.rst +++ b/auth_oidc/README.rst @@ -52,16 +52,16 @@ Example configuration with OpenID Connect implicit flow. This configuration is not recommended because it exposes the access token to the client, and in logs. -# configure a new web application in Azure with OpenID and implicit flow (see - the `provider documentation - `_) -# in this application the redirect url must be be "/auth_oauth/signin" and of course this URL should be reachable from - Azure -# create a new authentication provider in Odoo with the following - parameters (see the `portal documentation - `_ - for more information): +1. configure a new web application in Azure with OpenID and implicit flow (see + the `provider documentation + `_) +2. in this application the redirect url must be be "/auth_oauth/signin" and of course this URL should be reachable from + Azure +3. create a new authentication provider in Odoo with the following + parameters (see the `portal documentation + `_ + for more information): * Provider Name: Azure * Auth Flow: OpenID Connect @@ -80,10 +80,10 @@ Example configuration with OpenID Connect authorization code flow. In Keycloak: -# configure a new Client -# make sure Authorization Code Flow is Enabled. -# configure the client Access Type as "confidential" and take note of the client secret in the Credentials tab -# configure the redirect url to be "/auth_oauth/signin" +1. configure a new Client +2. make sure Authorization Code Flow is Enabled. +3. configure the client Access Type as "confidential" and take note of the client secret in the Credentials tab +4. configure the redirect url to be "/auth_oauth/signin" In Odoo, create a new Oauth Provider with the following parameters: diff --git a/auth_oidc/__manifest__.py b/auth_oidc/__manifest__.py index cdbf492ec0..c269c61185 100644 --- a/auth_oidc/__manifest__.py +++ b/auth_oidc/__manifest__.py @@ -4,7 +4,7 @@ { "name": "Authentication OpenID Connect", - "version": "15.0.1.0.0", + "version": "15.0.1.0.1", "license": "AGPL-3", "author": ( "ICTSTUDIO, André Schenkels, " diff --git a/auth_oidc/readme/CONFIGURE.rst b/auth_oidc/readme/CONFIGURE.rst index 74ef8ad38d..58e20f0abb 100644 --- a/auth_oidc/readme/CONFIGURE.rst +++ b/auth_oidc/readme/CONFIGURE.rst @@ -5,16 +5,16 @@ Example configuration with OpenID Connect implicit flow. This configuration is not recommended because it exposes the access token to the client, and in logs. -# configure a new web application in Azure with OpenID and implicit flow (see - the `provider documentation - `_) -# in this application the redirect url must be be "/auth_oauth/signin" and of course this URL should be reachable from - Azure -# create a new authentication provider in Odoo with the following - parameters (see the `portal documentation - `_ - for more information): +1. configure a new web application in Azure with OpenID and implicit flow (see + the `provider documentation + `_) +2. in this application the redirect url must be be "/auth_oauth/signin" and of course this URL should be reachable from + Azure +3. create a new authentication provider in Odoo with the following + parameters (see the `portal documentation + `_ + for more information): * Provider Name: Azure * Auth Flow: OpenID Connect @@ -33,10 +33,10 @@ Example configuration with OpenID Connect authorization code flow. In Keycloak: -# configure a new Client -# make sure Authorization Code Flow is Enabled. -# configure the client Access Type as "confidential" and take note of the client secret in the Credentials tab -# configure the redirect url to be "/auth_oauth/signin" +1. configure a new Client +2. make sure Authorization Code Flow is Enabled. +3. configure the client Access Type as "confidential" and take note of the client secret in the Credentials tab +4. configure the redirect url to be "/auth_oauth/signin" In Odoo, create a new Oauth Provider with the following parameters: diff --git a/auth_oidc/static/description/index.html b/auth_oidc/static/description/index.html index 737081829c..1a37324c66 100644 --- a/auth_oidc/static/description/index.html +++ b/auth_oidc/static/description/index.html @@ -410,16 +410,16 @@

Setup for Microsoft Azure

Example configuration with OpenID Connect implicit flow. This configuration is not recommended because it exposes the access token to the client, and in logs.

-
-
# configure a new web application in Azure with OpenID and implicit flow (see
-
the provider documentation)
-
# in this application the redirect url must be be “<url of your
-
server>/auth_oauth/signin” and of course this URL should be reachable from -Azure
-
# create a new authentication provider in Odoo with the following
-
parameters (see the portal documentation -for more information):
-
+
    +
  1. configure a new web application in Azure with OpenID and implicit flow (see +the provider documentation)
    2. +
  2. in this application the redirect url must be be “<url of your +server>/auth_oauth/signin” and of course this URL should be reachable from +Azure
    3. +
  3. create a new authentication provider in Odoo with the following +parameters (see the portal documentation +for more information):
    4. +
  • Provider Name: Azure
  • Auth Flow: OpenID Connect
    • @@ -435,10 +435,12 @@

    Setup for Microsoft Azure

    Setup for Keycloak

    Example configuration with OpenID Connect authorization code flow.

    In Keycloak:

    -

    # configure a new Client -# make sure Authorization Code Flow is Enabled. -# configure the client Access Type as “confidential” and take note of the client secret in the Credentials tab -# configure the redirect url to be “<url of your server>/auth_oauth/signin”

    +
      +
    1. configure a new Client
      2. +
    2. make sure Authorization Code Flow is Enabled.
      3. +
    3. configure the client Access Type as “confidential” and take note of the client secret in the Credentials tab
      4. +
    4. configure the redirect url to be “<url of your server>/auth_oauth/signin”
      5. +

    In Odoo, create a new Oauth Provider with the following parameters:

    • Provider name: Keycloak (or any name you like that identify your keycloak