From 2867831b7c05f933157e209dfb69d7573c47e46f Mon Sep 17 00:00:00 2001 From: Karl Kemister-Sheppard Date: Thu, 10 Jul 2025 14:41:55 +1000 Subject: [PATCH 1/2] DOC-3244: Fix typo in JWT token claims description for On-Premises documentation. --- ...t-from-word-and-export-to-word-autorization-on-premises.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/partials/individually-licensed-components/import-from-word-and-export-to-word/import-from-word-and-export-to-word-autorization-on-premises.adoc b/modules/ROOT/partials/individually-licensed-components/import-from-word-and-export-to-word/import-from-word-and-export-to-word-autorization-on-premises.adoc index 444a629f2d..2936791f3c 100644 --- a/modules/ROOT/partials/individually-licensed-components/import-from-word-and-export-to-word/import-from-word-and-export-to-word-autorization-on-premises.adoc +++ b/modules/ROOT/partials/individually-licensed-components/import-from-word-and-export-to-word/import-from-word-and-export-to-word-autorization-on-premises.adoc @@ -17,7 +17,7 @@ If the `SECRET_KEY` is not setup during the installation, then {pluginname} On-P * it is not issued in the future (e.i. the `iat` timestamp cannot be newer than the current time), * it has not expired yet. -Tokens for the {pluginname} On-Premises do not require any additional claims such as the environment ID (which is specific for Collaboration Server On-Premises), the token can be created with an empty payload. +Tokens for the {pluginname} On-Premises do not require any additional claims such as the aud (which is specific to cloud-based document converters), so the token can be created with an empty payload. If the specific use case involves sending requests from a backend server, then JWT tokens can be generated locally, as shown in the below request example. From dd9a1878507d7c50992a76af154d1b1ac47c47c5 Mon Sep 17 00:00:00 2001 From: Karl Kemister-Sheppard Date: Fri, 11 Jul 2025 08:47:05 +1000 Subject: [PATCH 2/2] Update modules/ROOT/partials/individually-licensed-components/import-from-word-and-export-to-word/import-from-word-and-export-to-word-autorization-on-premises.adoc Co-authored-by: Andrew Herron --- ...t-from-word-and-export-to-word-autorization-on-premises.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/partials/individually-licensed-components/import-from-word-and-export-to-word/import-from-word-and-export-to-word-autorization-on-premises.adoc b/modules/ROOT/partials/individually-licensed-components/import-from-word-and-export-to-word/import-from-word-and-export-to-word-autorization-on-premises.adoc index 2936791f3c..180ceac642 100644 --- a/modules/ROOT/partials/individually-licensed-components/import-from-word-and-export-to-word/import-from-word-and-export-to-word-autorization-on-premises.adoc +++ b/modules/ROOT/partials/individually-licensed-components/import-from-word-and-export-to-word/import-from-word-and-export-to-word-autorization-on-premises.adoc @@ -17,7 +17,7 @@ If the `SECRET_KEY` is not setup during the installation, then {pluginname} On-P * it is not issued in the future (e.i. the `iat` timestamp cannot be newer than the current time), * it has not expired yet. -Tokens for the {pluginname} On-Premises do not require any additional claims such as the aud (which is specific to cloud-based document converters), so the token can be created with an empty payload. +Tokens for the {pluginname} On-Premises do not require any additional claims such as the `aud` (which is specific to cloud-based document converters), so the token can be created with an empty payload. If the specific use case involves sending requests from a backend server, then JWT tokens can be generated locally, as shown in the below request example.