UiPath Documentation
robot
2026.10
false
Robot admin guide

Configuring package signature verification

Configure NuGet package signature verification for UiPath Robot by setting the validation mode and listing trusted signers in NuGet.config.

Package signature is a tool used by NuGet packages to verify their source as being trustworthy. This verification is done using a certificate that helps confirm the identity of the entity that has issued or created the package.

When you enable the certificate check, UiPath validates whether the packages being used come from an approved author or a permitted repository, enhancing the security of the deployment by ensuring that only reliable packages are used.

Validation modes​

Values for the validation mode parameter signatureValidationMode decide what kind of packages can be installed.

  • If you use accept, you can install both signed and unsigned packages.
  • If you use require, you can only install a package if the signing details have to match the ones from the <trustedSigners> section of the NuGet.config file.

Manual setup for signature verification​

The UiPath Platform Installer always writes signatureValidationMode to the NuGet.config file. It sets it to accept, unless you turn on Enforce signed execution (ENFORCE_SIGNED_EXECUTION), in which case it sets require and lists UiPath as a trusted signer.

Important:

Use Enforce signed execution or ENFORCE_SIGNED_EXECUTION as the supported way to require signed packages. On every update, the Platform Installer sets signatureValidationMode in NuGet.config from ENFORCE_SIGNED_EXECUTION, and removes the <trustedSigners> node unless ENFORCE_SIGNED_EXECUTION is true. A manual edit of these settings is lost on update when you did not enforce signed execution.

To change the validation mode or the trusted signers by hand, edit the NuGet.config file, set the signatureValidationMode parameter, and list the trusted signers.

Important:
  • If you use the NuGet.org feed, add it for both accept and require validation modes, as NuGet announces the whole repository as signed.
  • If you do no want to use package signature verification, make sure to remove the <trustedSigners> tag from the NuGet.config file.

Enabling package signatures​

You can configure the package signature either during installation, or post-installation, by editing the NuGet.config file:

  1. (Recommended) During installation with the UiPath Platform Installer: select Enforce signed execution in the Robot settings, or set "ENFORCE_SIGNED_EXECUTION": "true" for the Robot package in a silent installation. The installer sets signatureValidationMode to require and adds UiPath to the trusted signers.
  2. After installation: in the NuGet.config file, add the signatureValidationMode parameter, and set it to require. The next update of the Robot resets this edit unless Enforce signed execution is on for that update.
    Note:

    By default, the NuGet.config file is stored in the Robot installation folder: %ProgramFiles%\UiPathPlatform\Robot\<version> for a per-machine installation, or %LocalAppData%\Programs\UiPathPlatform\Robot\<version> for a per-user installation.

For the changes in the NuGet.config file to take effect:

  1. Restart the Robot Service.
  2. Remove all existing NuGet packages from %userprofile%\.nuget\packages, or from the folder set in packagesInstallationFolder in UiPath.config. For a Service Mode robot, %userprofile% is the profile of the account that the job runs as.
  3. Restart Studio and Assistant.

Adding trusted sources​

To download, install, and run packages signed with a specific certificate, add it as a trusted source.

  1. Open the NuGet.config file.
  2. Under the <trustedSigners> section, add the <author> tag, and provide the values of a trusted author. For example, UiPath has the following author values:
    <config>
         <add key="signatureValidationMode" value="require" />
    </config>
    <trustedSigners>
       <author name="UiPath">
          <certificate fingerprint="D179174EBC1E180D656BFB15BE369DEA8A17C178230FAC7771BF5446940C290C" hashAlgorithm="SHA256" allowUntrustedRoot="false"/>
          <certificate fingerprint="ABD1E1BB749DDC96B46A1DBD91B93A2D8B3B5572D1E20A52F6165ED96FC117E0" hashAlgorithm="SHA256" allowUntrustedRoot="false" />
          <certificate fingerprint="A96ADDC7455443CF702A887BC153CF7844038E2E88081D676C57DDD90EC90245" hashAlgorithm="SHA256" allowUntrustedRoot="false" />
       </author>
    </trustedSigners>
    <config>
         <add key="signatureValidationMode" value="require" />
    </config>
    <trustedSigners>
       <author name="UiPath">
          <certificate fingerprint="D179174EBC1E180D656BFB15BE369DEA8A17C178230FAC7771BF5446940C290C" hashAlgorithm="SHA256" allowUntrustedRoot="false"/>
          <certificate fingerprint="ABD1E1BB749DDC96B46A1DBD91B93A2D8B3B5572D1E20A52F6165ED96FC117E0" hashAlgorithm="SHA256" allowUntrustedRoot="false" />
          <certificate fingerprint="A96ADDC7455443CF702A887BC153CF7844038E2E88081D676C57DDD90EC90245" hashAlgorithm="SHA256" allowUntrustedRoot="false" />
       </author>
    </trustedSigners>
    
  3. Under the <trustedSigners> section, add the <repository> tag, and provide values of a trusted repository. For example, UiPath has the following repository values:
    <config>
         <add key="signatureValidationMode" value="require" />
    </config>
    <trustedSigners>
       <repository name="UiPathRepository" serviceIndex="https://gallery.uipath.com/api/v3/index.json">
          <certificate fingerprint="D179174EBC1E180D656BFB15BE369DEA8A17C178230FAC7771BF5446940C290C" hashAlgorithm="SHA256" allowUntrustedRoot="false" />
          <certificate fingerprint="ABD1E1BB749DDC96B46A1DBD91B93A2D8B3B5572D1E20A52F6165ED96FC117E0" hashAlgorithm="SHA256" allowUntrustedRoot="false" />
          <certificate fingerprint="A96ADDC7455443CF702A887BC153CF7844038E2E88081D676C57DDD90EC90245" hashAlgorithm="SHA256" allowUntrustedRoot="false" />
       </repository>
    </trustedSigners>
    <config>
         <add key="signatureValidationMode" value="require" />
    </config>
    <trustedSigners>
       <repository name="UiPathRepository" serviceIndex="https://gallery.uipath.com/api/v3/index.json">
          <certificate fingerprint="D179174EBC1E180D656BFB15BE369DEA8A17C178230FAC7771BF5446940C290C" hashAlgorithm="SHA256" allowUntrustedRoot="false" />
          <certificate fingerprint="ABD1E1BB749DDC96B46A1DBD91B93A2D8B3B5572D1E20A52F6165ED96FC117E0" hashAlgorithm="SHA256" allowUntrustedRoot="false" />
          <certificate fingerprint="A96ADDC7455443CF702A887BC153CF7844038E2E88081D676C57DDD90EC90245" hashAlgorithm="SHA256" allowUntrustedRoot="false" />
       </repository>
    </trustedSigners>
    
  4. To add a list of trusted owners, add the <owners> tag, and provide the names of the trusted authors. This allows only packages signed by multiple trusted authors.
    <config>
         <add key="signatureValidationMode" value="require" />
    </config>
    <trustedSigners>
        <repository name="UiPath Repository" serviceIndex="https://uipath.repository">
            <certificate fingerprint="1234512345123451234512345123123123123123123123123123112312312E5" hashAlgorithm="SHA256" allowUntrustedRoot="true" />
            <owners>Author1;Author2;Author3</owners> 
        </repository>
    </trustedSigners>
    <config>
         <add key="signatureValidationMode" value="require" />
    </config>
    <trustedSigners>
        <repository name="UiPath Repository" serviceIndex="https://uipath.repository">
            <certificate fingerprint="1234512345123451234512345123123123123123123123123123112312312E5" hashAlgorithm="SHA256" allowUntrustedRoot="true" />
            <owners>Author1;Author2;Author3</owners> 
        </repository>
    </trustedSigners>
    

Was this page helpful?

Connect

Need help? Support(opens in new window)

Want to learn? UiPath Academy(opens in new window)

Have questions? UiPath Forum(opens in new window)

Stay updated