Just to follow up.
We've identified the problem in our certificate management framework and made changes to ensure that timely notifications will go out for all certificates. There are some specific monitoring improvements that will also be made to the servers that support the web single sign-on services in order to avoid this situation from re-occurring.
On 4/16/18, 21:15 , "Technology Discussion at UVM on behalf of Greg Kuchyt" <[log in to unmask] on behalf of [log in to unmask]> wrote:
Apologies to all for this.
A minor matter of administrivia in how I configured this certificate in our certificate management framework led to no notification being generated about this upcoming expiry. I'll be working tomorrow to identify any other certificates that may be susceptible to this and will work to address that.
On 4/16/18, 21:03 , "Technology Discussion at UVM on behalf of Travis Bartlett" <[log in to unmask] on behalf of [log in to unmask]> wrote:
The WebAuth certificate expired this evening (Monday, April 16).
The connection to webauth.uvm.edu is still encrypted, however, the expired cert results in web browsers alerting users that the connection to webauth.uvm.edu may not be secure.
SAA is currently working to renew the certificate now.
Sorry for any inconvenience this has caused.