diff --git a/en/asgardeo/docs/apis/organization-apis/restapis/application.yaml b/en/asgardeo/docs/apis/organization-apis/restapis/application.yaml index 08a879d1bd..afbe079dc3 100644 --- a/en/asgardeo/docs/apis/organization-apis/restapis/application.yaml +++ b/en/asgardeo/docs/apis/organization-apis/restapis/application.yaml @@ -1235,7 +1235,7 @@ components: type: type: string description: " - - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overriden with values defined at the tenant level. + - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overridden with values defined at the tenant level. - USER_DEFINED type indicates that the application will use a user-defined authentication sequence." enum: diff --git a/en/asgardeo/docs/apis/organization-apis/restapis/org-application-mgt.yaml b/en/asgardeo/docs/apis/organization-apis/restapis/org-application-mgt.yaml index 41cf0a087d..349de7796e 100644 --- a/en/asgardeo/docs/apis/organization-apis/restapis/org-application-mgt.yaml +++ b/en/asgardeo/docs/apis/organization-apis/restapis/org-application-mgt.yaml @@ -2087,7 +2087,7 @@ components: type: string description: " " enum: diff --git a/en/asgardeo/docs/apis/restapis/application-management.yaml b/en/asgardeo/docs/apis/restapis/application-management.yaml index 0d7c914803..3e65040e1b 100644 --- a/en/asgardeo/docs/apis/restapis/application-management.yaml +++ b/en/asgardeo/docs/apis/restapis/application-management.yaml @@ -4948,7 +4948,7 @@ components: type: string description: " " enum: diff --git a/en/identity-server/7.0.0/docs/apis/organization-apis/restapis/application.yaml b/en/identity-server/7.0.0/docs/apis/organization-apis/restapis/application.yaml index dcd2c6fa52..311efdcd5d 100644 --- a/en/identity-server/7.0.0/docs/apis/organization-apis/restapis/application.yaml +++ b/en/identity-server/7.0.0/docs/apis/organization-apis/restapis/application.yaml @@ -1226,7 +1226,7 @@ components: type: type: string description: " - - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overriden with values defined at the tenant level. + - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overridden with values defined at the tenant level. - USER_DEFINED type indicates that the application will use a user-defined authentication sequence." enum: diff --git a/en/identity-server/7.0.0/docs/apis/restapis/application.yaml b/en/identity-server/7.0.0/docs/apis/restapis/application.yaml index d08fa2e3be..292279a2ef 100644 --- a/en/identity-server/7.0.0/docs/apis/restapis/application.yaml +++ b/en/identity-server/7.0.0/docs/apis/restapis/application.yaml @@ -4962,7 +4962,7 @@ components: type: type: string description: " - - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overriden with values defined at the tenant level. + - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overridden with values defined at the tenant level. - USER_DEFINED type indicates that the application will use a user-defined authentication sequence." enum: diff --git a/en/identity-server/7.0.0/docs/deploy/configure/session-persistence.md b/en/identity-server/7.0.0/docs/deploy/configure/session-persistence.md index ee38231f5a..ac47b6643a 100644 --- a/en/identity-server/7.0.0/docs/deploy/configure/session-persistence.md +++ b/en/identity-server/7.0.0/docs/deploy/configure/session-persistence.md @@ -102,7 +102,7 @@ The `[session_data.cleanup]` section is related to the cleaning up of session da ## Importance of correct `Deletechunksize` In the world of the World Wide Web, sessions are the simplest way to store data for individual users against a unique session ID. These can be used to persist state information between page requests. When all -the requests ad responses that come to a page per day are considered, that is a large amount. Due to this reason, the session data stored in the “IDN\_AUTH\_SESSION\_STORE ” table in the WSO2CARBON\_DB of WSO2 IS is high. This table fills up quickly if your system receives too many loads of requests. +the requests and responses that come to a page per day are considered, that is a large amount. Due to this reason, the session data stored in the “IDN\_AUTH\_SESSION\_STORE ” table in the WSO2CARBON\_DB of WSO2 IS is high. This table fills up quickly if your system receives too many loads of requests. After a certain period, these session data are not necessary. To stop the exponential table growth, a Session Clean Up Task in predefined time intervals is run via a script. If this storing session data is huge, the data that need to be deleted also will come in bulk. diff --git a/en/identity-server/7.1.0/docs/apis/organization-apis/restapis/application.yaml b/en/identity-server/7.1.0/docs/apis/organization-apis/restapis/application.yaml index dcd2c6fa52..311efdcd5d 100644 --- a/en/identity-server/7.1.0/docs/apis/organization-apis/restapis/application.yaml +++ b/en/identity-server/7.1.0/docs/apis/organization-apis/restapis/application.yaml @@ -1226,7 +1226,7 @@ components: type: type: string description: " - - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overriden with values defined at the tenant level. + - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overridden with values defined at the tenant level. - USER_DEFINED type indicates that the application will use a user-defined authentication sequence." enum: diff --git a/en/identity-server/7.1.0/docs/apis/organization-apis/restapis/org-application-mgt.yaml b/en/identity-server/7.1.0/docs/apis/organization-apis/restapis/org-application-mgt.yaml index e36ce2d0b6..5f2fa76883 100644 --- a/en/identity-server/7.1.0/docs/apis/organization-apis/restapis/org-application-mgt.yaml +++ b/en/identity-server/7.1.0/docs/apis/organization-apis/restapis/org-application-mgt.yaml @@ -2105,7 +2105,7 @@ components: type: type: string description: " - - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overriden with values defined at the tenant level. + - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overridden with values defined at the tenant level. - USER_DEFINED type indicates that the application will use a user-defined authentication sequence." enum: diff --git a/en/identity-server/7.1.0/docs/apis/restapis/application.yaml b/en/identity-server/7.1.0/docs/apis/restapis/application.yaml index f62e52420c..70365a4a06 100644 --- a/en/identity-server/7.1.0/docs/apis/restapis/application.yaml +++ b/en/identity-server/7.1.0/docs/apis/restapis/application.yaml @@ -5063,7 +5063,7 @@ components: type: type: string description: " - - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overriden with values defined at the tenant level. + - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overridden with values defined at the tenant level. - USER_DEFINED type indicates that the application will use a user-defined authentication sequence." enum: diff --git a/en/identity-server/7.1.0/docs/deploy/configure/session-persistence.md b/en/identity-server/7.1.0/docs/deploy/configure/session-persistence.md index ee38231f5a..ac47b6643a 100644 --- a/en/identity-server/7.1.0/docs/deploy/configure/session-persistence.md +++ b/en/identity-server/7.1.0/docs/deploy/configure/session-persistence.md @@ -102,7 +102,7 @@ The `[session_data.cleanup]` section is related to the cleaning up of session da ## Importance of correct `Deletechunksize` In the world of the World Wide Web, sessions are the simplest way to store data for individual users against a unique session ID. These can be used to persist state information between page requests. When all -the requests ad responses that come to a page per day are considered, that is a large amount. Due to this reason, the session data stored in the “IDN\_AUTH\_SESSION\_STORE ” table in the WSO2CARBON\_DB of WSO2 IS is high. This table fills up quickly if your system receives too many loads of requests. +the requests and responses that come to a page per day are considered, that is a large amount. Due to this reason, the session data stored in the “IDN\_AUTH\_SESSION\_STORE ” table in the WSO2CARBON\_DB of WSO2 IS is high. This table fills up quickly if your system receives too many loads of requests. After a certain period, these session data are not necessary. To stop the exponential table growth, a Session Clean Up Task in predefined time intervals is run via a script. If this storing session data is huge, the data that need to be deleted also will come in bulk. diff --git a/en/identity-server/7.2.0/docs/apis/organization-apis/restapis/application.yaml b/en/identity-server/7.2.0/docs/apis/organization-apis/restapis/application.yaml index dcd2c6fa52..311efdcd5d 100644 --- a/en/identity-server/7.2.0/docs/apis/organization-apis/restapis/application.yaml +++ b/en/identity-server/7.2.0/docs/apis/organization-apis/restapis/application.yaml @@ -1226,7 +1226,7 @@ components: type: type: string description: " - - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overriden with values defined at the tenant level. + - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overridden with values defined at the tenant level. - USER_DEFINED type indicates that the application will use a user-defined authentication sequence." enum: diff --git a/en/identity-server/7.2.0/docs/apis/organization-apis/restapis/org-application-mgt.yaml b/en/identity-server/7.2.0/docs/apis/organization-apis/restapis/org-application-mgt.yaml index a4499aee5f..2cb329a05a 100644 --- a/en/identity-server/7.2.0/docs/apis/organization-apis/restapis/org-application-mgt.yaml +++ b/en/identity-server/7.2.0/docs/apis/organization-apis/restapis/org-application-mgt.yaml @@ -2425,7 +2425,7 @@ components: type: type: string description: " - - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overriden with values defined at the tenant level. + - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overridden with values defined at the tenant level. - USER_DEFINED type indicates that the application will use a user-defined authentication sequence." enum: diff --git a/en/identity-server/7.2.0/docs/deploy/configure/session-persistence.md b/en/identity-server/7.2.0/docs/deploy/configure/session-persistence.md index ee38231f5a..ac47b6643a 100644 --- a/en/identity-server/7.2.0/docs/deploy/configure/session-persistence.md +++ b/en/identity-server/7.2.0/docs/deploy/configure/session-persistence.md @@ -102,7 +102,7 @@ The `[session_data.cleanup]` section is related to the cleaning up of session da ## Importance of correct `Deletechunksize` In the world of the World Wide Web, sessions are the simplest way to store data for individual users against a unique session ID. These can be used to persist state information between page requests. When all -the requests ad responses that come to a page per day are considered, that is a large amount. Due to this reason, the session data stored in the “IDN\_AUTH\_SESSION\_STORE ” table in the WSO2CARBON\_DB of WSO2 IS is high. This table fills up quickly if your system receives too many loads of requests. +the requests and responses that come to a page per day are considered, that is a large amount. Due to this reason, the session data stored in the “IDN\_AUTH\_SESSION\_STORE ” table in the WSO2CARBON\_DB of WSO2 IS is high. This table fills up quickly if your system receives too many loads of requests. After a certain period, these session data are not necessary. To stop the exponential table growth, a Session Clean Up Task in predefined time intervals is run via a script. If this storing session data is huge, the data that need to be deleted also will come in bulk. diff --git a/en/identity-server/7.3.0/docs/apis/organization-apis/restapis/application.yaml b/en/identity-server/7.3.0/docs/apis/organization-apis/restapis/application.yaml index 6f5c748992..a7c2f8b479 100644 --- a/en/identity-server/7.3.0/docs/apis/organization-apis/restapis/application.yaml +++ b/en/identity-server/7.3.0/docs/apis/organization-apis/restapis/application.yaml @@ -1230,7 +1230,7 @@ components: type: type: string description: " - - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overriden with values defined at the tenant level. + - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overridden with values defined at the tenant level. - USER_DEFINED type indicates that the application will use a user-defined authentication sequence." enum: diff --git a/en/identity-server/7.3.0/docs/apis/organization-apis/restapis/org-application-mgt.yaml b/en/identity-server/7.3.0/docs/apis/organization-apis/restapis/org-application-mgt.yaml index e3d05b3c0d..e2e00bb288 100644 --- a/en/identity-server/7.3.0/docs/apis/organization-apis/restapis/org-application-mgt.yaml +++ b/en/identity-server/7.3.0/docs/apis/organization-apis/restapis/org-application-mgt.yaml @@ -2470,7 +2470,7 @@ components: type: type: string description: " - - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overriden with values defined at the tenant level. + - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overridden with values defined at the tenant level. - USER_DEFINED type indicates that the application will use a user-defined authentication sequence." enum: diff --git a/en/identity-server/7.3.0/docs/deploy/configure/session-persistence.md b/en/identity-server/7.3.0/docs/deploy/configure/session-persistence.md index ee38231f5a..ac47b6643a 100644 --- a/en/identity-server/7.3.0/docs/deploy/configure/session-persistence.md +++ b/en/identity-server/7.3.0/docs/deploy/configure/session-persistence.md @@ -102,7 +102,7 @@ The `[session_data.cleanup]` section is related to the cleaning up of session da ## Importance of correct `Deletechunksize` In the world of the World Wide Web, sessions are the simplest way to store data for individual users against a unique session ID. These can be used to persist state information between page requests. When all -the requests ad responses that come to a page per day are considered, that is a large amount. Due to this reason, the session data stored in the “IDN\_AUTH\_SESSION\_STORE ” table in the WSO2CARBON\_DB of WSO2 IS is high. This table fills up quickly if your system receives too many loads of requests. +the requests and responses that come to a page per day are considered, that is a large amount. Due to this reason, the session data stored in the “IDN\_AUTH\_SESSION\_STORE ” table in the WSO2CARBON\_DB of WSO2 IS is high. This table fills up quickly if your system receives too many loads of requests. After a certain period, these session data are not necessary. To stop the exponential table growth, a Session Clean Up Task in predefined time intervals is run via a script. If this storing session data is huge, the data that need to be deleted also will come in bulk. diff --git a/en/identity-server/next/docs/apis/organization-apis/restapis/application.yaml b/en/identity-server/next/docs/apis/organization-apis/restapis/application.yaml index 6f5c748992..a7c2f8b479 100644 --- a/en/identity-server/next/docs/apis/organization-apis/restapis/application.yaml +++ b/en/identity-server/next/docs/apis/organization-apis/restapis/application.yaml @@ -1230,7 +1230,7 @@ components: type: type: string description: " - - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overriden with values defined at the tenant level. + - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overridden with values defined at the tenant level. - USER_DEFINED type indicates that the application will use a user-defined authentication sequence." enum: diff --git a/en/identity-server/next/docs/apis/organization-apis/restapis/org-application-mgt.yaml b/en/identity-server/next/docs/apis/organization-apis/restapis/org-application-mgt.yaml index e3d05b3c0d..e2e00bb288 100644 --- a/en/identity-server/next/docs/apis/organization-apis/restapis/org-application-mgt.yaml +++ b/en/identity-server/next/docs/apis/organization-apis/restapis/org-application-mgt.yaml @@ -2470,7 +2470,7 @@ components: type: type: string description: " - - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overriden with values defined at the tenant level. + - DEFAULT type indicates that the application will use the default authentication sequence specified at the tenant level. When the DEFAULT type is used, the information given in the other fields of the AuthenticationSequence will be ignored and overridden with values defined at the tenant level. - USER_DEFINED type indicates that the application will use a user-defined authentication sequence." enum: diff --git a/en/identity-server/next/docs/deploy/configure/session-persistence.md b/en/identity-server/next/docs/deploy/configure/session-persistence.md index ee38231f5a..ac47b6643a 100644 --- a/en/identity-server/next/docs/deploy/configure/session-persistence.md +++ b/en/identity-server/next/docs/deploy/configure/session-persistence.md @@ -102,7 +102,7 @@ The `[session_data.cleanup]` section is related to the cleaning up of session da ## Importance of correct `Deletechunksize` In the world of the World Wide Web, sessions are the simplest way to store data for individual users against a unique session ID. These can be used to persist state information between page requests. When all -the requests ad responses that come to a page per day are considered, that is a large amount. Due to this reason, the session data stored in the “IDN\_AUTH\_SESSION\_STORE ” table in the WSO2CARBON\_DB of WSO2 IS is high. This table fills up quickly if your system receives too many loads of requests. +the requests and responses that come to a page per day are considered, that is a large amount. Due to this reason, the session data stored in the “IDN\_AUTH\_SESSION\_STORE ” table in the WSO2CARBON\_DB of WSO2 IS is high. This table fills up quickly if your system receives too many loads of requests. After a certain period, these session data are not necessary. To stop the exponential table growth, a Session Clean Up Task in predefined time intervals is run via a script. If this storing session data is huge, the data that need to be deleted also will come in bulk. diff --git a/en/includes/deploy/configure-console-hostname.md b/en/includes/deploy/configure-console-hostname.md index 26745729ae..3a59a3ea3d 100644 --- a/en/includes/deploy/configure-console-hostname.md +++ b/en/includes/deploy/configure-console-hostname.md @@ -13,7 +13,7 @@ This guide outlines two strategies to achieve this in {{product_name}}: The most robust security model involves physically or logically separating the infrastructure into two planes: a **Control Plane** for administration and a **Data Plane** for runtime operations. -![data-plane-control-plane-seperation]({{base_path}}/assets/img/deploy/data-plane-control-plane-seperation.png) +![data-plane-control-plane-separation]({{base_path}}/assets/img/deploy/data-plane-control-plane-seperation.png) ### 1. Control plane (internal)