From 4e1eab722a0c6e209f150a94ded17f6419bb8c6d Mon Sep 17 00:00:00 2001 From: Mark Kachkaev <37276742+mkachk@users.noreply.github.com> Date: Fri, 1 Aug 2025 12:18:15 -0400 Subject: [PATCH 1/4] Update configuration.md --- docsource/configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsource/configuration.md b/docsource/configuration.md index dd91b63..b6afe0d 100644 --- a/docsource/configuration.md +++ b/docsource/configuration.md @@ -20,7 +20,7 @@ GlobalSign supports the following Root certificates: [GlobalSign Root Certificat Each additional Root will require a separate CA setup. ## Valid GlobalSign SAN Usage -GlobalSign supports specific combinations of SAN types with certain products. For example, a Private IP can only be used as a SAN with a `PV_INTRA` Certificate. +GlobalSign supports specific combinations of SAN types with certain GlobalSign products. For example, a Private IP can only be used as a SAN with a `PV_INTRA` Certificate. Please refer to the GlobalSign documentation for more information on SAN usage: [GlobalSign MSSL API User Guide (Section 2.2.5)](https://www.globalsign.com/en/repository/globalsign-mssl-api-user-guide.pdf) From e00e53d695a0e13a0c64e400a0fa6cc921b413dd Mon Sep 17 00:00:00 2001 From: Keyfactor Date: Fri, 1 Aug 2025 16:21:46 +0000 Subject: [PATCH 2/4] Update generated docs --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9efda9a..35a37ad 100644 --- a/README.md +++ b/README.md @@ -126,7 +126,7 @@ This extension uses the contact information of the GCC Domain point of contact f ## Valid GlobalSign SAN Usage -GlobalSign supports specific combinations of SAN types with certain products. For example, a Private IP can only be used as a SAN with a `PV_INTRA` Certificate. +GlobalSign supports specific combinations of SAN types with certain GlobalSign products. For example, a Private IP can only be used as a SAN with a `PV_INTRA` Certificate. Please refer to the GlobalSign documentation for more information on SAN usage: [GlobalSign MSSL API User Guide (Section 2.2.5)](https://www.globalsign.com/en/repository/globalsign-mssl-api-user-guide.pdf) ## Enrollment Fields From 8e30f7e1592a53f96774780ac2c82dcad03c6ca8 Mon Sep 17 00:00:00 2001 From: Mark Kachkaev <37276742+mkachk@users.noreply.github.com> Date: Fri, 1 Aug 2025 12:22:50 -0400 Subject: [PATCH 3/4] Update integration-manifest.json to fix release dir --- integration-manifest.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/integration-manifest.json b/integration-manifest.json index 0c4a78b..aa3424f 100644 --- a/integration-manifest.json +++ b/integration-manifest.json @@ -9,7 +9,7 @@ "description": "GlobalSign MSSL plugin for the AnyCA REST Gateway framework", "gateway_framework": "25.2.0", "release_dir": "globalsign-mssl-caplugin/bin/Release/", - "release_project": "cscglobal-caplugin/CSCGlobalCAPlugin.csproj", + "release_project": "globalsign-mssl-caplugin/GlobalSignCAPlugin.csproj", "about": { "carest": { "ca_plugin_config": [ @@ -89,4 +89,4 @@ ] } } -} \ No newline at end of file +} From 64c7470f449c8ab11585c095c8b7a0282ea545c3 Mon Sep 17 00:00:00 2001 From: Keyfactor Date: Fri, 1 Aug 2025 16:25:52 +0000 Subject: [PATCH 4/4] Update generated docs --- integration-manifest.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/integration-manifest.json b/integration-manifest.json index aa3424f..49a628a 100644 --- a/integration-manifest.json +++ b/integration-manifest.json @@ -89,4 +89,4 @@ ] } } -} +} \ No newline at end of file