Merge pull request wso2#4581 from divyaamunugama/minor

[IS] Image size fix
divyaamunugama · May 8, 2024 · 51a25af · 51a25af
2 parents 14e0240 + 37be931
commit 51a25af
Show file tree

Hide file tree

Showing 5 changed files with 7 additions and 7 deletions.
diff --git 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-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
@@ -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.
 

diff --git 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 `<IS_HOME>/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
@@ -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;"}
-Original file line number
+Diff line change
@@ Expand Up @@
     ```
     !!! 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 `<IS_HOME>/repository/conf` directory.
         ```json
@@ Expand Down @@