Re: Digicert code-signing

2022-01-27 Thread Rémy Maucherat
On Thu, Jan 27, 2022 at 10:12 PM Mark Thomas  wrote:
>
> Primarily for release managers.
>
> Your API key and certificate have expiry dates. By default this is a
> year after you created them. The error message when they have expired
> just indicates that the credentials are invalid.
>
> If you get unexpected signing errors - check the validity of your API
> key and cert (you can do this through the DigiCert one web interface).

Thanks for the reminder. It's best to go in and check it a little once
in a while (I had forgotten about the website already ...) rather than
be stuck in the middle of some early July release.

Rémy

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Digicert code-signing

2022-01-27 Thread Mark Thomas

Primarily for release managers.

Your API key and certificate have expiry dates. By default this is a 
year after you created them. The error message when they have expired 
just indicates that the credentials are invalid.


If you get unexpected signing errors - check the validity of your API 
key and cert (you can do this through the DigiCert one web interface).


Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Digicert code signing

2021-01-06 Thread Mark Thomas
All,

Just a heads up that the annual renewal of the client certificate we use
to access the Digicert code signing service for release builds is
currently failing with a 404 mid-way through the renewal process.

The current certificate is valid until for another 4 weeks so we should
have time to sort this out. I am currently attempting to contact support.

On a related topic I was expecting this service to have been retired by
now and replaced with the new one. I got access to the test instance and
it is very configurable (which is good) but I quickly got to the point
where I needed to talk through with Digicert how best to configure it
for the ASF. Things have been stick at this point for a couple of months
now.

And now support are denying the service still exists... Sigh. I'll
update the list with progress - if I ever manage to make some.

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org