This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 4%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETK%3C/text%3E%3C/svg%3E)
Hello,
It does not seem like we can use a timestamp server that is HTTPS. Are there any restrictions for using HTTPS URLs with Azure Trusted Signing?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(48, 68%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKS%3C/text%3E%3C/svg%3E)
Hi @Thai K. Nguyen,
Based on your query, I understand you would like to the URLs to be used for timestamp.
As per our Microsoft document, you need to use: http://timestamp.acs.microsoft.com/ as timestamp Authority.
Prerequisites:
To complete the steps in this article, you need:
Here is the info: Trusted Signing certificates have a three-day validity, so time stamping is critical for continued successful validation of a signature beyond that three-day validity period. Trusted Signing recommends the use of Trusted Signing’s Microsoft Public RSA Time Stamping Authority: http://timestamp.acs.microsoft.com/.
I hope this information is helpful. Please feel free to reach out if you have any further questions.
Hello Kancharla,
Thanks for the response, but it did not address my question specifically, which was to see if there is an HTTPS timestamp server that can be used instead of the HTTP one, which in the doc you referenced, MS says is recommended and NOT required for timestamping (at least it can be interpreted that way)
Trusted Signing recommends the use of Trusted Signing’s Microsoft Public RSA Time Stamping Authority:
http://timestamp.acs.microsoft.com/.
NOTE: I'm able to successfully sign files using other HTTP URLs, and not just the one MS recommends. However, I'm unable to sign successfully with any HTTPS timestamp URLs.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 52%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
We are working on making timestampers available via https, don't have a date yet.
Hi @Thai K. Nguyen,,
As per our community confirmation, Https timestamp server is not yet available. We would request to go with our recommended Http timestamp server itself. You can provide your product feedback on the same using our Azure feedback forum. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Hi @Thai K. Nguyen,
Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.