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/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