Artifact Signing
A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
before a singing request we supply our own CorrelationId in the metadata.json file to track which project uses the most sign requests.
We've setup monitoring to a storage account. I've downloaded the logs and found that our custom CorrelationId is nowhere to be found.
I think the CorrelationId is overwritten by a new Guid every time.
Is this a bug in the Microsoft.Trusted.Signing.Client?
Thanks,
Michael
A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)