How to use Azure Trusted Signing in Azure Pipelines? I am getting a timeout error.

Question

I am using Trusted Signing using this command in Pipelines: Invoke-TrustedSigning -Endpoint https://eus.codesigning.azure.net -CodeSigningAccountName aaa -CertificateProfileName aaa-app -FilesFolder D:\... -FilesFolderFilter exe -FileDigest SHA256 -TimestampRfc3161 'http://timestamp.acs.microsoft.com' -TimestampDigest SHA256

There is only one exe to sign.

I am getting this error:

Submitting digest for signing...
The Trusted Signing service could not finish the request within the allotted time of 300 seconds. This may happen if you are signing a large number of files. You can try to increase the value of the 'Timeout' parameter which is 300 seconds by default.
At C:\Program Files\WindowsPowerShell\Modules\TrustedSigning\0.4.1\SignTool\SignTool.psm1:192 char:9
+         throw $timeoutError
+         ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (The Trusted Sig...nds by default.:String) [], RuntimeException
    + FullyQualifiedErrorId : The Trusted Signing service could not finish the request within the allotted time of 300 seconds. This may happen if you are signing a large number of files. You can try to increase the value of the 'Timeout' parameter which is 300 seconds by default.

I need to use Invoke-TrustedSigning for my electron-builder configuration. I can't use this Pinelines extension with electron-builder: https://marketplace.visualstudio.com/items?itemName=VisualStudioClient.TrustedSigning

I was able to sign using a test Windows VM with the same AZURE_CLIENT_ID, AZURE_TENANT_ID, AZURE_CLIENT_SECRET and Invoke-TrustedSigning

Answer 1

My fixed my issue. I didn't supply these values correctly: AZURE_CLIENT_ID, AZURE_TENANT_ID, AZURE_CLIENT_SECRET and the issue manifested differently in Pipelines vs on a test Windows VM (with intentionally incorrect values)