From 9918f79533bb5bf6eb767b39c9b002a9c541759e Mon Sep 17 00:00:00 2001 From: wso2 Date: Tue, 7 May 2024 14:02:56 +0530 Subject: [PATCH 1/2] image size fix --- .../authentication/oidc/implement-auth-code-with-pkce.md | 4 ++-- en/includes/guides/authentication/oidc/implement-auth-code.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/en/includes/guides/authentication/oidc/implement-auth-code-with-pkce.md b/en/includes/guides/authentication/oidc/implement-auth-code-with-pkce.md index 77544bb981..2a4ede816f 100644 --- a/en/includes/guides/authentication/oidc/implement-auth-code-with-pkce.md +++ b/en/includes/guides/authentication/oidc/implement-auth-code-with-pkce.md @@ -8,7 +8,7 @@ For public clients, it is recommended to use [PKCE](https://datatracker.ietf.org The following diagram explains how this flow works with {{ product_name }}. -![Authorization code flow with PKCE]({{base_path}}/assets/img/guides/applications/oidc/auth_code_flow_with_pkce.png) +![Authorization code flow with PKCE]({{base_path}}/assets/img/guides/applications/oidc/auth_code_flow_with_pkce.png){: width="700" style="border: 0.3px solid lightgrey;"} As shown above, you need to configure your application to get the authorization code from {{ product_name }}, and then exchange it for the required tokens. @@ -108,7 +108,7 @@ After receiving the authorization code, the application has to exchange it to ge === "cURL" ```bash - curl --location --request POST '{token_endpoint_url}' \ + curl --location --request POST '{{ product_url_format }}/oauth2/token' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data-urlencode 'code={authorization_code}' \ --data-urlencode 'grant_type=authorization_code' \ diff --git a/en/includes/guides/authentication/oidc/implement-auth-code.md b/en/includes/guides/authentication/oidc/implement-auth-code.md index 6f81b08dd5..eb3c0f3f06 100644 --- a/en/includes/guides/authentication/oidc/implement-auth-code.md +++ b/en/includes/guides/authentication/oidc/implement-auth-code.md @@ -4,7 +4,7 @@ See the instructions given below to implement login with OpenID Connect in your The following diagram explains how this flow works with {{ product_name }}: -![Authorization code flow]({{base_path}}/assets/img/guides/applications/oidc/auth_code_flow.png) +![Authorization code flow]({{base_path}}/assets/img/guides/applications/oidc/auth_code_flow.png){: width="700" style="border: 0.3px solid lightgrey;"} As shown above, you need to configure your application to get the authorization code from {{ product_name }}, and then exchange it for the required tokens. From 37be931537fde2984dadb09d18f54ffe4238d253 Mon Sep 17 00:00:00 2001 From: wso2 Date: Wed, 8 May 2024 10:39:40 +0530 Subject: [PATCH 2/2] image size fixes --- .../guides/authentication/oidc/discover-oidc-configs.md | 3 ++- .../guides/authentication/oidc/implement-login-with-par.md | 1 - .../guides/authentication/oidc/private-key-jwt-client-auth.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/en/includes/guides/authentication/oidc/discover-oidc-configs.md b/en/includes/guides/authentication/oidc/discover-oidc-configs.md index 7fb523d48f..eac856939a 100644 --- a/en/includes/guides/authentication/oidc/discover-oidc-configs.md +++ b/en/includes/guides/authentication/oidc/discover-oidc-configs.md @@ -94,7 +94,8 @@ You can get the endpoints from the console as follows: 2. Select an OIDC application from the list. 3. Go to the **Info** tab of the application and find the server endpoints to your organization. - ![app-help-panel-for-endpoints]({{base_path}}/assets/img/guides/applications/app-endpoint-help.png) + + ![app-help-panel-for-endpoints]({{base_path}}/assets/img/guides/applications/app-endpoint-help.png){: width="700" style="border: 0.3px solid lightgrey;"} ## What's next? diff --git a/en/includes/guides/authentication/oidc/implement-login-with-par.md b/en/includes/guides/authentication/oidc/implement-login-with-par.md index ae5279082f..2e203bf96b 100644 --- a/en/includes/guides/authentication/oidc/implement-login-with-par.md +++ b/en/includes/guides/authentication/oidc/implement-login-with-par.md @@ -59,7 +59,6 @@ You will receive a response with the request_uri and the time of expiry. ``` !!! note - - {{product_name}} uses the prefix, `urn:ietf:params:oauth:par:request_uri:` for the request_uri. The `/authorize` endpoint processes the request as initiated with PAR, only if the request_uri is of this format. - By default, the request_uri expires after 60 seconds. You can change the time of expiry (e.g. 90 seconds), by adding the following configuration to the `deployment.toml` file found in the `/repository/conf` directory. ```json diff --git a/en/includes/guides/authentication/oidc/private-key-jwt-client-auth.md b/en/includes/guides/authentication/oidc/private-key-jwt-client-auth.md index 6d717a6104..2751a4634a 100644 --- a/en/includes/guides/authentication/oidc/private-key-jwt-client-auth.md +++ b/en/includes/guides/authentication/oidc/private-key-jwt-client-auth.md @@ -31,7 +31,7 @@ Register the client application in {{ product_name }} as follows: 2. Go to the **Protocol** tab of the new application and configure the required grant type. - ![oidc protocols]({{base_path}}/assets/img/guides/applications/oidc/oidc_protocols.png) + ![oidc protocols]({{base_path}}/assets/img/guides/applications/oidc/oidc_protocols.png){: width="700" style="border: 0.3px solid lightgrey;"} ## Prepare the private key and public key @@ -223,4 +223,4 @@ To enable token reuse in {{ product_name }}. 2. Under **Login Security**, click **Private Key JWT Client Authentication (OIDC)**. 3. Switch on the toggle to enable token reuse. - ![configure JWT reuse]({{base_path}}/assets/img/guides/applications/oidc/private-key-jwt-config.png) + ![configure JWT reuse]({{base_path}}/assets/img/guides/applications/oidc/private-key-jwt-config.png){: width="700" style="border: 0.3px solid lightgrey;"}