From 073d50c6007460da5991e2f89ca78eb27a1aa6dc Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Wed, 3 Jun 2026 07:27:05 +0000 Subject: [PATCH 1/2] =?UTF-8?q?docs:=20fix=20#1059=20=E2=80=94=20update=20?= =?UTF-8?q?broken=20Signing=20Key=20Utility=20download=20links?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Replace directorymanager path with groupid path in download URLs per the correct links from security advisory ADV-2025-004. Co-Authored-By: Claude --- .../admincenter/service/securityservice/signkeyutility.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/directorymanager/11.1/admincenter/service/securityservice/signkeyutility.md b/docs/directorymanager/11.1/admincenter/service/securityservice/signkeyutility.md index 0814ddc85e..1ca4c593af 100644 --- a/docs/directorymanager/11.1/admincenter/service/securityservice/signkeyutility.md +++ b/docs/directorymanager/11.1/admincenter/service/securityservice/signkeyutility.md @@ -31,11 +31,11 @@ following URLs: - Pre v11.1 (2.1, 2.2, 2.3, 2.4) - [https://releases.netwrix.com/products/directorymanager/11.0/directorymanager-Signing-Key-Utility-11.0.0.zip](https://releases.netwrix.com/products/directorymanager/11.0/directorymanager-Signing-Key-Utility-11.0.0.zip) + [https://releases.netwrix.com/products/groupid/11.0/groupid-Signing-Key-Utility-11.0.0.zip](https://releases.netwrix.com/products/groupid/11.0/groupid-Signing-Key-Utility-11.0.0.zip) - For v11.1 - [https://releases.netwrix.com/products/directorymanager/11.1/directorymanager-Signing-Key-Utility-11.1.0.zip](https://releases.netwrix.com/products/directorymanager/11.1/directorymanager-Signing-Key-Utility-11.1.0.zip) + [https://releases.netwrix.com/products/groupid/11.1/groupid-Signing-Key-Utility-11.1.0.zip](https://releases.netwrix.com/products/groupid/11.1/groupid-Signing-Key-Utility-11.1.0.zip) The file is downloaded into a folder as per your browser’s download settings. Unzip the file into a folder. From 908b29da15fb16db9f90e82b678e9990cf66954c Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Wed, 3 Jun 2026 07:30:29 +0000 Subject: [PATCH 2/2] fix(vale): auto-fix style issues (Vale + Dale) --- .../service/securityservice/signkeyutility.md | 38 +++++++++---------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/docs/directorymanager/11.1/admincenter/service/securityservice/signkeyutility.md b/docs/directorymanager/11.1/admincenter/service/securityservice/signkeyutility.md index 1ca4c593af..ea997419e1 100644 --- a/docs/directorymanager/11.1/admincenter/service/securityservice/signkeyutility.md +++ b/docs/directorymanager/11.1/admincenter/service/securityservice/signkeyutility.md @@ -6,20 +6,20 @@ sidebar_position: 30 # Signing Key Utility -This utility was created to remediate the vulnerability described in Netwrix security advisory +Netwrix created this utility to remediate the vulnerability described in Netwrix security advisory ADV-2025-004 ([https://security.netwrix.com/Advisories/ADV-2025-004](https://security.netwrix.com/Advisories/ADV-2025-004)). -Running this utility will cause a new customer-specific signing key to be generated and used by the -application. See the Generate a Signing Key section for additional information. +Running this utility generates a new customer-specific signing key for the application to use. See +the Generate a Signing Key section for additional information. -Having generated the customer-specific signing key, your existing schedules will not work as their -authentication mechanism will no longer be considered valid. Therefore, the authentication mechanism -must be updated for schedules as well. See the Update Schedules section for additional information. +After you generate the customer-specific signing key, your existing schedules will not work because +their authentication mechanism will no longer be valid. Therefore, you must also update the +authentication mechanism for schedules. See the Update Schedules section for additional information. -In case you are running multiple instances of Directory Manager for load balancing and high -availability, using this utility you can export the newly generated signing key and then import it -to other Directory Manager instances. See the following sections for information on how to export -and import the signing key: +If you run multiple instances of Directory Manager for load balancing and high availability, you can +use this utility to export the newly generated signing key and then import it to other Directory +Manager instances. See the following sections for information on how to export and import the +signing key: - Export a Signing Key - Import a Signing Key @@ -37,7 +37,7 @@ following URLs: [https://releases.netwrix.com/products/groupid/11.1/groupid-Signing-Key-Utility-11.1.0.zip](https://releases.netwrix.com/products/groupid/11.1/groupid-Signing-Key-Utility-11.1.0.zip) -The file is downloaded into a folder as per your browser’s download settings. Unzip the file into a +Your browser downloads the file into a folder based on its download settings. Unzip the file into a folder. ## Generate a Signing Key @@ -50,17 +50,17 @@ Generate the new signing key on your Directory Manager server machine. ::: -Follow the steps to generate a new signing key. +To generate a new signing key: -Step 1 – At the Windows Command prompt, go to the folder where you have placed the utility. +1. At the Windows Command prompt, go to the folder where you have placed the utility. -Step 2 – Type the following command at the prompt: +2. Enter the following command at the prompt: ``` SigningKeyUtility.exe GenerateSigningKey -u “” -s “” -d “” -i ``` -Step 3 – Provide the password of SQL server for authentication. +3. Provide the password of SQL server for authentication. Parameters: @@ -89,7 +89,7 @@ SigningKeyUtility.exe UpdateSchedulers -u “” -s “