diff --git a/en/asgardeo/docs/apis/organization-apis/restapis/association-management-by-admin.yaml b/en/asgardeo/docs/apis/organization-apis/restapis/association-management-by-admin.yaml index 99d6ca2d35..0c36edc41d 100644 --- a/en/asgardeo/docs/apis/organization-apis/restapis/association-management-by-admin.yaml +++ b/en/asgardeo/docs/apis/organization-apis/restapis/association-management-by-admin.yaml @@ -502,7 +502,7 @@ components: example: 1 description: | This represents whether the API should stop processing the operations if any of them fail. The subsequent - operations after the the fail count is reached will not be processed. + operations after the fail count is reached will not be processed. If set to 0 or not set, the API will continue processing the operations even if some of them fail. operations: type: array diff --git a/en/asgardeo/docs/apis/restapis/association-management-by-admin.yaml b/en/asgardeo/docs/apis/restapis/association-management-by-admin.yaml index 8805fe015e..cd1da03d32 100644 --- a/en/asgardeo/docs/apis/restapis/association-management-by-admin.yaml +++ b/en/asgardeo/docs/apis/restapis/association-management-by-admin.yaml @@ -502,7 +502,7 @@ components: example: 1 description: | This represents whether the API should stop processing the operations if any of them fail. The subsequent - operations after the the fail count is reached will not be processed. + operations after the fail count is reached will not be processed. If set to 0 or not set, the API will continue processing the operations even if some of them fail. operations: type: array diff --git a/en/asgardeo/docs/apis/restapis/user-account-recovery.yaml b/en/asgardeo/docs/apis/restapis/user-account-recovery.yaml index b965e67d9a..26da6aafcf 100644 --- a/en/asgardeo/docs/apis/restapis/user-account-recovery.yaml +++ b/en/asgardeo/docs/apis/restapis/user-account-recovery.yaml @@ -17,7 +17,7 @@ paths: notifications. - Use the returned __recoveryCode__ and the __channelId__ with - __username recover api__ to confirm the the username recovery and to + __username recover api__ to confirm the username recovery and to receive recovery notifications via the channel specified by the user. Scope(Permission) required: `internal_user_recovery_create` diff --git a/en/identity-server/7.0.0/docs/apis/restapis/user-account-recovery-v1.yaml b/en/identity-server/7.0.0/docs/apis/restapis/user-account-recovery-v1.yaml index ad0418e8f4..137c7d38a4 100644 --- a/en/identity-server/7.0.0/docs/apis/restapis/user-account-recovery-v1.yaml +++ b/en/identity-server/7.0.0/docs/apis/restapis/user-account-recovery-v1.yaml @@ -27,7 +27,7 @@ paths: notifications. - Use the returned __recoveryCode__ and the __channelId__ with - __username recover api__ to confirm the the username recovery and to + __username recover api__ to confirm the username recovery and to receive recovery notifications via the channel specified by the user. Scope(Permission) required: `internal_user_recovery_create` diff --git a/en/identity-server/7.0.0/docs/apis/restapis/user-account-recovery-v2.yaml b/en/identity-server/7.0.0/docs/apis/restapis/user-account-recovery-v2.yaml index 2b7d06530c..5ea1d1a67f 100644 --- a/en/identity-server/7.0.0/docs/apis/restapis/user-account-recovery-v2.yaml +++ b/en/identity-server/7.0.0/docs/apis/restapis/user-account-recovery-v2.yaml @@ -17,7 +17,7 @@ paths: notifications. - Use the returned __recoveryCode__ and the __channelId__ with - __username recover api__ to confirm the the username recovery and to + __username recover api__ to confirm the username recovery and to receive recovery notifications via the channel specified by the user. Scope(Permission) required: `internal_user_recovery_create` diff --git a/en/identity-server/7.0.0/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md b/en/identity-server/7.0.0/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md index b7b388260a..54940835be 100644 --- a/en/identity-server/7.0.0/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md +++ b/en/identity-server/7.0.0/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md @@ -286,7 +286,7 @@ using the respective permalinks. Following are the columns of the table. ## UM_SYSTEM_USER_ROLE -Storing the system roles assigned to the the system users is done with +Storing the system roles assigned to the system users is done with this table. `UM_USER_NAME` contains the username of the system user. `UM_ROLE_ID` contains the ID of the system role which points to the `UM_ID` column of the `UM_SYSTEM_ROLE` table. The `wso2.anonymous.role` system role is by default assigned to the `wso2.anonymous.user` system diff --git a/en/identity-server/7.0.0/docs/get-started/try-your-own-app/java-ee-saml.md b/en/identity-server/7.0.0/docs/get-started/try-your-own-app/java-ee-saml.md index b793e58924..e45bdefa24 100644 --- a/en/identity-server/7.0.0/docs/get-started/try-your-own-app/java-ee-saml.md +++ b/en/identity-server/7.0.0/docs/get-started/try-your-own-app/java-ee-saml.md @@ -56,7 +56,7 @@ Follow the steps given below to initialize the SAML agent. ### Create the configuration file -To initialize the SAML agent, you need a property file with the configurations such as the the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file. +To initialize the SAML agent, you need a property file with the configurations such as the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file. Create a file named **sample-app.properties** inside the **/src/main/resources** directory, using the content below. diff --git a/en/identity-server/7.1.0/docs/apis/restapis/user-account-recovery-v1.yaml b/en/identity-server/7.1.0/docs/apis/restapis/user-account-recovery-v1.yaml index ad0418e8f4..137c7d38a4 100644 --- a/en/identity-server/7.1.0/docs/apis/restapis/user-account-recovery-v1.yaml +++ b/en/identity-server/7.1.0/docs/apis/restapis/user-account-recovery-v1.yaml @@ -27,7 +27,7 @@ paths: notifications. - Use the returned __recoveryCode__ and the __channelId__ with - __username recover api__ to confirm the the username recovery and to + __username recover api__ to confirm the username recovery and to receive recovery notifications via the channel specified by the user. Scope(Permission) required: `internal_user_recovery_create` diff --git a/en/identity-server/7.1.0/docs/apis/restapis/user-account-recovery-v2.yaml b/en/identity-server/7.1.0/docs/apis/restapis/user-account-recovery-v2.yaml index 2b7d06530c..5ea1d1a67f 100644 --- a/en/identity-server/7.1.0/docs/apis/restapis/user-account-recovery-v2.yaml +++ b/en/identity-server/7.1.0/docs/apis/restapis/user-account-recovery-v2.yaml @@ -17,7 +17,7 @@ paths: notifications. - Use the returned __recoveryCode__ and the __channelId__ with - __username recover api__ to confirm the the username recovery and to + __username recover api__ to confirm the username recovery and to receive recovery notifications via the channel specified by the user. Scope(Permission) required: `internal_user_recovery_create` diff --git a/en/identity-server/7.1.0/docs/complete-guides/nextjs/register-an-application.md b/en/identity-server/7.1.0/docs/complete-guides/nextjs/register-an-application.md index 0e71ffb971..1ce3acd4d2 100644 --- a/en/identity-server/7.1.0/docs/complete-guides/nextjs/register-an-application.md +++ b/en/identity-server/7.1.0/docs/complete-guides/nextjs/register-an-application.md @@ -29,6 +29,6 @@ Make a note of the following values from the **Protocol** and **Info** tabs of t * **`client-id`** from the **Protocol** tab. * **`client-secret`** from the **Protocol** tab. -* **`issuer`** from from the **Info** tab. +* **`issuer`** from the **Info** tab. {% include "../../../../../includes/complete-guides/nextjs/register-an-application.md" %} diff --git a/en/identity-server/7.1.0/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md b/en/identity-server/7.1.0/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md index b7b388260a..54940835be 100644 --- a/en/identity-server/7.1.0/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md +++ b/en/identity-server/7.1.0/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md @@ -286,7 +286,7 @@ using the respective permalinks. Following are the columns of the table. ## UM_SYSTEM_USER_ROLE -Storing the system roles assigned to the the system users is done with +Storing the system roles assigned to the system users is done with this table. `UM_USER_NAME` contains the username of the system user. `UM_ROLE_ID` contains the ID of the system role which points to the `UM_ID` column of the `UM_SYSTEM_ROLE` table. The `wso2.anonymous.role` system role is by default assigned to the `wso2.anonymous.user` system diff --git a/en/identity-server/7.1.0/docs/get-started/try-your-own-app/java-ee-saml.md b/en/identity-server/7.1.0/docs/get-started/try-your-own-app/java-ee-saml.md index 326ad8cb4a..7c78b7db1d 100644 --- a/en/identity-server/7.1.0/docs/get-started/try-your-own-app/java-ee-saml.md +++ b/en/identity-server/7.1.0/docs/get-started/try-your-own-app/java-ee-saml.md @@ -56,7 +56,7 @@ Follow the steps given below to initialize the SAML agent. ### Create the configuration file -To initialize the SAML agent, you need a property file with the configurations such as the the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file. +To initialize the SAML agent, you need a property file with the configurations such as the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file. Create a file named **sample-app.properties** inside the **/src/main/resources** directory, using the content below. diff --git a/en/identity-server/7.1.0/docs/guides/multitenancy/manage-tenants.md b/en/identity-server/7.1.0/docs/guides/multitenancy/manage-tenants.md index d2850f0450..2d7e7db556 100644 --- a/en/identity-server/7.1.0/docs/guides/multitenancy/manage-tenants.md +++ b/en/identity-server/7.1.0/docs/guides/multitenancy/manage-tenants.md @@ -75,7 +75,7 @@ Follow the steps given below to add a new root organization from the {{ product_ -5. Once a new root organization is created, it will be listed in the the **Root Organization** listing page as shown below. +5. Once a new root organization is created, it will be listed in the **Root Organization** listing page as shown below. ![Root Organization Listing]({{base_path}}/assets/img/guides/multitenancy/root-organizaiton-listing.png) diff --git a/en/identity-server/7.2.0/docs/apis/organization-apis/restapis/association-management-by-admin.yaml b/en/identity-server/7.2.0/docs/apis/organization-apis/restapis/association-management-by-admin.yaml index 1f0ea61d61..93e0ecad64 100644 --- a/en/identity-server/7.2.0/docs/apis/organization-apis/restapis/association-management-by-admin.yaml +++ b/en/identity-server/7.2.0/docs/apis/organization-apis/restapis/association-management-by-admin.yaml @@ -502,7 +502,7 @@ components: example: 1 description: | This represents whether the API should stop processing the operations if any of them fail. The subsequent - operations after the the fail count is reached will not be processed. + operations after the fail count is reached will not be processed. If set to 0 or not set, the API will continue processing the operations even if some of them fail. operations: type: array diff --git a/en/identity-server/7.2.0/docs/apis/restapis/association-management-by-admin.yaml b/en/identity-server/7.2.0/docs/apis/restapis/association-management-by-admin.yaml index ee1a0f21a8..3fd71ad104 100644 --- a/en/identity-server/7.2.0/docs/apis/restapis/association-management-by-admin.yaml +++ b/en/identity-server/7.2.0/docs/apis/restapis/association-management-by-admin.yaml @@ -502,7 +502,7 @@ components: example: 1 description: | This represents whether the API should stop processing the operations if any of them fail. The subsequent - operations after the the fail count is reached will not be processed. + operations after the fail count is reached will not be processed. If set to 0 or not set, the API will continue processing the operations even if some of them fail. operations: type: array diff --git a/en/identity-server/7.2.0/docs/apis/restapis/user-account-recovery-v1.yaml b/en/identity-server/7.2.0/docs/apis/restapis/user-account-recovery-v1.yaml index ad0418e8f4..137c7d38a4 100644 --- a/en/identity-server/7.2.0/docs/apis/restapis/user-account-recovery-v1.yaml +++ b/en/identity-server/7.2.0/docs/apis/restapis/user-account-recovery-v1.yaml @@ -27,7 +27,7 @@ paths: notifications. - Use the returned __recoveryCode__ and the __channelId__ with - __username recover api__ to confirm the the username recovery and to + __username recover api__ to confirm the username recovery and to receive recovery notifications via the channel specified by the user. Scope(Permission) required: `internal_user_recovery_create` diff --git a/en/identity-server/7.2.0/docs/apis/restapis/user-account-recovery-v2.yaml b/en/identity-server/7.2.0/docs/apis/restapis/user-account-recovery-v2.yaml index 2b7d06530c..5ea1d1a67f 100644 --- a/en/identity-server/7.2.0/docs/apis/restapis/user-account-recovery-v2.yaml +++ b/en/identity-server/7.2.0/docs/apis/restapis/user-account-recovery-v2.yaml @@ -17,7 +17,7 @@ paths: notifications. - Use the returned __recoveryCode__ and the __channelId__ with - __username recover api__ to confirm the the username recovery and to + __username recover api__ to confirm the username recovery and to receive recovery notifications via the channel specified by the user. Scope(Permission) required: `internal_user_recovery_create` diff --git a/en/identity-server/7.2.0/docs/complete-guides/nextjs/register-an-application.md b/en/identity-server/7.2.0/docs/complete-guides/nextjs/register-an-application.md index 0e71ffb971..1ce3acd4d2 100644 --- a/en/identity-server/7.2.0/docs/complete-guides/nextjs/register-an-application.md +++ b/en/identity-server/7.2.0/docs/complete-guides/nextjs/register-an-application.md @@ -29,6 +29,6 @@ Make a note of the following values from the **Protocol** and **Info** tabs of t * **`client-id`** from the **Protocol** tab. * **`client-secret`** from the **Protocol** tab. -* **`issuer`** from from the **Info** tab. +* **`issuer`** from the **Info** tab. {% include "../../../../../includes/complete-guides/nextjs/register-an-application.md" %} diff --git a/en/identity-server/7.2.0/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md b/en/identity-server/7.2.0/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md index b7b388260a..54940835be 100644 --- a/en/identity-server/7.2.0/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md +++ b/en/identity-server/7.2.0/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md @@ -286,7 +286,7 @@ using the respective permalinks. Following are the columns of the table. ## UM_SYSTEM_USER_ROLE -Storing the system roles assigned to the the system users is done with +Storing the system roles assigned to the system users is done with this table. `UM_USER_NAME` contains the username of the system user. `UM_ROLE_ID` contains the ID of the system role which points to the `UM_ID` column of the `UM_SYSTEM_ROLE` table. The `wso2.anonymous.role` system role is by default assigned to the `wso2.anonymous.user` system diff --git a/en/identity-server/7.2.0/docs/get-started/try-your-own-app/java-ee-saml.md b/en/identity-server/7.2.0/docs/get-started/try-your-own-app/java-ee-saml.md index 326ad8cb4a..7c78b7db1d 100644 --- a/en/identity-server/7.2.0/docs/get-started/try-your-own-app/java-ee-saml.md +++ b/en/identity-server/7.2.0/docs/get-started/try-your-own-app/java-ee-saml.md @@ -56,7 +56,7 @@ Follow the steps given below to initialize the SAML agent. ### Create the configuration file -To initialize the SAML agent, you need a property file with the configurations such as the the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file. +To initialize the SAML agent, you need a property file with the configurations such as the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file. Create a file named **sample-app.properties** inside the **/src/main/resources** directory, using the content below. diff --git a/en/identity-server/7.2.0/docs/guides/multitenancy/manage-tenants.md b/en/identity-server/7.2.0/docs/guides/multitenancy/manage-tenants.md index 9edeed7d0f..379aa76e4b 100644 --- a/en/identity-server/7.2.0/docs/guides/multitenancy/manage-tenants.md +++ b/en/identity-server/7.2.0/docs/guides/multitenancy/manage-tenants.md @@ -82,7 +82,7 @@ Follow the steps given below to add a new root organization from the {{ product_ !!! note Keep the **Organization Name** field blank to use the **Organization Handle** (tenant domain) as the name. -5. Once a new root organization is created, it will be listed in the the **Root Organization** listing page as shown below. +5. Once a new root organization is created, it will be listed in the **Root Organization** listing page as shown below. ![Root Organization Listing]({{base_path}}/assets/img/guides/multitenancy/root-organizaiton-listing.png) diff --git a/en/identity-server/7.3.0/docs/apis/organization-apis/restapis/association-management-by-admin.yaml b/en/identity-server/7.3.0/docs/apis/organization-apis/restapis/association-management-by-admin.yaml index 1f0ea61d61..93e0ecad64 100644 --- a/en/identity-server/7.3.0/docs/apis/organization-apis/restapis/association-management-by-admin.yaml +++ b/en/identity-server/7.3.0/docs/apis/organization-apis/restapis/association-management-by-admin.yaml @@ -502,7 +502,7 @@ components: example: 1 description: | This represents whether the API should stop processing the operations if any of them fail. The subsequent - operations after the the fail count is reached will not be processed. + operations after the fail count is reached will not be processed. If set to 0 or not set, the API will continue processing the operations even if some of them fail. operations: type: array diff --git a/en/identity-server/7.3.0/docs/apis/restapis/association-management-by-admin.yaml b/en/identity-server/7.3.0/docs/apis/restapis/association-management-by-admin.yaml index ee1a0f21a8..3fd71ad104 100644 --- a/en/identity-server/7.3.0/docs/apis/restapis/association-management-by-admin.yaml +++ b/en/identity-server/7.3.0/docs/apis/restapis/association-management-by-admin.yaml @@ -502,7 +502,7 @@ components: example: 1 description: | This represents whether the API should stop processing the operations if any of them fail. The subsequent - operations after the the fail count is reached will not be processed. + operations after the fail count is reached will not be processed. If set to 0 or not set, the API will continue processing the operations even if some of them fail. operations: type: array diff --git a/en/identity-server/7.3.0/docs/apis/restapis/user-account-recovery-v1.yaml b/en/identity-server/7.3.0/docs/apis/restapis/user-account-recovery-v1.yaml index ad0418e8f4..137c7d38a4 100644 --- a/en/identity-server/7.3.0/docs/apis/restapis/user-account-recovery-v1.yaml +++ b/en/identity-server/7.3.0/docs/apis/restapis/user-account-recovery-v1.yaml @@ -27,7 +27,7 @@ paths: notifications. - Use the returned __recoveryCode__ and the __channelId__ with - __username recover api__ to confirm the the username recovery and to + __username recover api__ to confirm the username recovery and to receive recovery notifications via the channel specified by the user. Scope(Permission) required: `internal_user_recovery_create` diff --git a/en/identity-server/7.3.0/docs/apis/restapis/user-account-recovery-v2.yaml b/en/identity-server/7.3.0/docs/apis/restapis/user-account-recovery-v2.yaml index 2b7d06530c..5ea1d1a67f 100644 --- a/en/identity-server/7.3.0/docs/apis/restapis/user-account-recovery-v2.yaml +++ b/en/identity-server/7.3.0/docs/apis/restapis/user-account-recovery-v2.yaml @@ -17,7 +17,7 @@ paths: notifications. - Use the returned __recoveryCode__ and the __channelId__ with - __username recover api__ to confirm the the username recovery and to + __username recover api__ to confirm the username recovery and to receive recovery notifications via the channel specified by the user. Scope(Permission) required: `internal_user_recovery_create` diff --git a/en/identity-server/next/docs/apis/organization-apis/restapis/association-management-by-admin.yaml b/en/identity-server/next/docs/apis/organization-apis/restapis/association-management-by-admin.yaml index 1f0ea61d61..93e0ecad64 100644 --- a/en/identity-server/next/docs/apis/organization-apis/restapis/association-management-by-admin.yaml +++ b/en/identity-server/next/docs/apis/organization-apis/restapis/association-management-by-admin.yaml @@ -502,7 +502,7 @@ components: example: 1 description: | This represents whether the API should stop processing the operations if any of them fail. The subsequent - operations after the the fail count is reached will not be processed. + operations after the fail count is reached will not be processed. If set to 0 or not set, the API will continue processing the operations even if some of them fail. operations: type: array diff --git a/en/identity-server/next/docs/apis/restapis/association-management-by-admin.yaml b/en/identity-server/next/docs/apis/restapis/association-management-by-admin.yaml index ee1a0f21a8..3fd71ad104 100644 --- a/en/identity-server/next/docs/apis/restapis/association-management-by-admin.yaml +++ b/en/identity-server/next/docs/apis/restapis/association-management-by-admin.yaml @@ -502,7 +502,7 @@ components: example: 1 description: | This represents whether the API should stop processing the operations if any of them fail. The subsequent - operations after the the fail count is reached will not be processed. + operations after the fail count is reached will not be processed. If set to 0 or not set, the API will continue processing the operations even if some of them fail. operations: type: array diff --git a/en/identity-server/next/docs/apis/restapis/user-account-recovery-v1.yaml b/en/identity-server/next/docs/apis/restapis/user-account-recovery-v1.yaml index ad0418e8f4..137c7d38a4 100644 --- a/en/identity-server/next/docs/apis/restapis/user-account-recovery-v1.yaml +++ b/en/identity-server/next/docs/apis/restapis/user-account-recovery-v1.yaml @@ -27,7 +27,7 @@ paths: notifications. - Use the returned __recoveryCode__ and the __channelId__ with - __username recover api__ to confirm the the username recovery and to + __username recover api__ to confirm the username recovery and to receive recovery notifications via the channel specified by the user. Scope(Permission) required: `internal_user_recovery_create` diff --git a/en/identity-server/next/docs/apis/restapis/user-account-recovery-v2.yaml b/en/identity-server/next/docs/apis/restapis/user-account-recovery-v2.yaml index 2b7d06530c..5ea1d1a67f 100644 --- a/en/identity-server/next/docs/apis/restapis/user-account-recovery-v2.yaml +++ b/en/identity-server/next/docs/apis/restapis/user-account-recovery-v2.yaml @@ -17,7 +17,7 @@ paths: notifications. - Use the returned __recoveryCode__ and the __channelId__ with - __username recover api__ to confirm the the username recovery and to + __username recover api__ to confirm the username recovery and to receive recovery notifications via the channel specified by the user. Scope(Permission) required: `internal_user_recovery_create` diff --git a/en/identity-server/next/docs/complete-guides/nextjs/register-an-application.md b/en/identity-server/next/docs/complete-guides/nextjs/register-an-application.md index e57e304f97..9f94c967dc 100644 --- a/en/identity-server/next/docs/complete-guides/nextjs/register-an-application.md +++ b/en/identity-server/next/docs/complete-guides/nextjs/register-an-application.md @@ -29,6 +29,6 @@ Make a note of the following values from the **Protocol** and **Info** tabs of t * **`client-id`** from the **Protocol** tab. * **`client-secret`** from the **Protocol** tab. -* **`issuer`** from from the **Info** tab. +* **`issuer`** from the **Info** tab. {% include "../../../../../includes/complete-guides/nextjs/register-an-application.md" %} diff --git a/en/identity-server/next/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md b/en/identity-server/next/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md index b7b388260a..54940835be 100644 --- a/en/identity-server/next/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md +++ b/en/identity-server/next/docs/deploy/configure/databases/data-dictionary/user-management-related-tables.md @@ -286,7 +286,7 @@ using the respective permalinks. Following are the columns of the table. ## UM_SYSTEM_USER_ROLE -Storing the system roles assigned to the the system users is done with +Storing the system roles assigned to the system users is done with this table. `UM_USER_NAME` contains the username of the system user. `UM_ROLE_ID` contains the ID of the system role which points to the `UM_ID` column of the `UM_SYSTEM_ROLE` table. The `wso2.anonymous.role` system role is by default assigned to the `wso2.anonymous.user` system diff --git a/en/identity-server/next/docs/get-started/try-your-own-app/java-ee-saml.md b/en/identity-server/next/docs/get-started/try-your-own-app/java-ee-saml.md index 326ad8cb4a..7c78b7db1d 100644 --- a/en/identity-server/next/docs/get-started/try-your-own-app/java-ee-saml.md +++ b/en/identity-server/next/docs/get-started/try-your-own-app/java-ee-saml.md @@ -56,7 +56,7 @@ Follow the steps given below to initialize the SAML agent. ### Create the configuration file -To initialize the SAML agent, you need a property file with the configurations such as the the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file. +To initialize the SAML agent, you need a property file with the configurations such as the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file. Create a file named **sample-app.properties** inside the **/src/main/resources** directory, using the content below. diff --git a/en/identity-server/next/docs/guides/multitenancy/manage-tenants.md b/en/identity-server/next/docs/guides/multitenancy/manage-tenants.md index 9edeed7d0f..379aa76e4b 100644 --- a/en/identity-server/next/docs/guides/multitenancy/manage-tenants.md +++ b/en/identity-server/next/docs/guides/multitenancy/manage-tenants.md @@ -82,7 +82,7 @@ Follow the steps given below to add a new root organization from the {{ product_ !!! note Keep the **Organization Name** field blank to use the **Organization Handle** (tenant domain) as the name. -5. Once a new root organization is created, it will be listed in the the **Root Organization** listing page as shown below. +5. Once a new root organization is created, it will be listed in the **Root Organization** listing page as shown below. ![Root Organization Listing]({{base_path}}/assets/img/guides/multitenancy/root-organizaiton-listing.png) diff --git a/en/includes/complete-guides/angular/register-an-application.md b/en/includes/complete-guides/angular/register-an-application.md index ae9edf052e..5c53a60850 100644 --- a/en/includes/complete-guides/angular/register-an-application.md +++ b/en/includes/complete-guides/angular/register-an-application.md @@ -20,6 +20,6 @@ Next, complete the wizard popup by providing a suitable name and an authorized r Make a note of the following values from the **Protocol** and **Info** tabs of the registered application. You will need them to configure the authentication SDK * **`client-id`** from the **Protocol** tab. -* **`issuer`** from from the **Info** tab. +* **`issuer`** from the **Info** tab. In this step, we have ve registered our Angular app as an application in the {{product_name}} console and generated the required metadata. Next, we will create a Angular app. diff --git a/en/includes/complete-guides/fesecurity/public-clients.md b/en/includes/complete-guides/fesecurity/public-clients.md index fbf18b9e92..0267cdbb0e 100644 --- a/en/includes/complete-guides/fesecurity/public-clients.md +++ b/en/includes/complete-guides/fesecurity/public-clients.md @@ -31,7 +31,7 @@ The IdP takes the code verifier sent in the token request and applies the same t This process ensures that if an attacker were to intercept the authorization code during the authorization phase, they wouldn't be able to exchange it for tokens. This is because they wouldn't possess the code verifier, a secret known only to the legitimate client. Since the code verifier is generated dynamically and is used only once, even if an attacker somehow obtains it, it would be useless for future requests. -PKCE is an important security improvement for frontend applications but at the same time it sounds like an extra burden for you to generate and process all these code challenges and code verifiers by yourself. The good news here is, following the security best practices such as secure by design, secure by default, most of the the frontend authentication SDKs automatically enable PKCE extension for you. For instance, WSO2 Identity Platform React SDK enables PKCE extension for your apps by default. Here is how you can enable it manually by setting the enable PKCE option to true in the WSO2 Identity Platform SDK configuration: +PKCE is an important security improvement for frontend applications but at the same time it sounds like an extra burden for you to generate and process all these code challenges and code verifiers by yourself. The good news here is, following the security best practices such as secure by design, secure by default, most of the frontend authentication SDKs automatically enable PKCE extension for you. For instance, WSO2 Identity Platform React SDK enables PKCE extension for your apps by default. Here is how you can enable it manually by setting the enable PKCE option to true in the WSO2 Identity Platform SDK configuration: ```javascript title="src/main.jsx" hl_lines="9" diff --git a/en/includes/quick-starts/springboot.md b/en/includes/quick-starts/springboot.md index dbbf8a03d6..744e352603 100644 --- a/en/includes/quick-starts/springboot.md +++ b/en/includes/quick-starts/springboot.md @@ -24,7 +24,7 @@ Make a note of the following values from the **Protocol** and **Info** tabs of t - **`client-id`** from the **Protocol** tab. - **`client-secret`** from the **Protocol** tab. -- **`issuer`** from from the **Info** tab. +- **`issuer`** from the **Info** tab. ## Create a Spring Boot app using Spring Initializr diff --git a/en/includes/references/extend/federation/write-a-custom-federated-authenticator.md b/en/includes/references/extend/federation/write-a-custom-federated-authenticator.md index c7e830cccc..81bcf3da13 100644 --- a/en/includes/references/extend/federation/write-a-custom-federated-authenticator.md +++ b/en/includes/references/extend/federation/write-a-custom-federated-authenticator.md @@ -295,7 +295,7 @@ To configure the custom federated authenticator for the application: 3. Select the sign in option configured. -4. Enter the credentials of the the new user created in the partner identity server. +4. Enter the credentials of the new user created in the partner identity server. The user is successfully authenticated by the partner Identity Server.