Signing Key Utility
Netwrix created this utility to remediate the vulnerability described in Netwrix security advisory ADV-2025-004 (https://security.netwrix.com/Advisories/ADV-2025-004). 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.
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.
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. To export and import the signing key, see the following sections:
- Export a Signing Key
- Import a Signing Key
Download the Utility
You can download the Netwrix Directory Manager (formerly GroupID) Signing Key Utility from the following URLs:
-
Pre v11.1 (2.1, 2.2, 2.3, 2.4)
https://releases.netwrix.com/products/groupid/11.0/groupid-Signing-Key-Utility-11.0.0.zip
-
For v11.1
https://releases.netwrix.com/products/groupid/11.1/groupid-Signing-Key-Utility-11.1.0.zip
Your browser downloads the file into a folder based on its download settings. Unzip the file into a folder.
Generate a Signing Key
Use the Netwrix Directory Manager (formerly GroupID) Signing Key Utility to generate a new signing key.
Generate the new signing key on your Directory Manager server machine.
To generate a new signing key:
-
At the Windows Command prompt, go to the folder that contains the utility.
-
Enter the following command at the prompt:
SigningKeyUtility.exe GenerateSigningKey -u “<DB username>” -s “<SQLServer name>” -d “<DB name>” -i
- Provide the password of SQL server for authentication.
Parameters:
-
-u — provide username of the SQL server where your database exists
-
-s — provide the name of the SQL server
-
-d — provide database name you are using with Directory Manager
-
-i — use this parameter if you are using SQL authentication.
If you are using Windows authentication, ignore this argument
Update Schedules
This command will update the signing key information in all the existing schedules for each identity store, except the Microsoft Entra ID store.
SigningKeyUtility.exe UpdateSchedulers -u “<DB username>” -s “<SQLServer name>” -d “<DB name>” -i
Parameters
- Use the same parameters given in the Generate a SigningKey section.
Export a Signing Key
If you are using multiple instances of Directory Manager, you need to export the newly generated signing key to other instances of Directory Manager. Enter the following command at the Windows Command prompt to export the signing key in .pfx. encrypted format with a password:
SigningKeyUtility.exe ExportSigningKey -o “<Folder location for signingkey export>”
Parameters
- -o — provide folder location where the utility will export the signing key
This command generates a password for the encrypted signing key. Copy it and store it securely for later use. The utility saves the encrypted signing key in the specified folder.
Import a Signing Key
Copy the newly generated signing key on the required Directory Manager instance. Enter the following command at the Windows Command prompt to import the encrypted .pfx signing key:
SigningKeyUtility.exe ImportSigningKey -n “<Folder location of encryption key>” -p “<Password of encryption key>” -u “<DB username>” -s “<SQLServer name>” -d “<DB name>” -i
Provide the password for SQL server authentication.
Parameters
-
-n — provide folder location to import the encrypted signing key from
-
-p — provide the password to decrypt the signing key
-
Use the same parameters given in the Generate a Signing Key section.