You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We run cicognara.org on our load-balancers. However, because the site does not have the .princeton.edu extension, we have been manually managing the cert for this site. We would like to manage the cert for cocognara.org the same way as all other certs for sites on the load-balancers.
Acceptance criteria
I can request a certificate for cicognara.org from Sectigo (preferably using our ansible playbook, but that is not a requirement)
I can set the certificates up for auto-renew through Sectigo using certbot
Implementation notes, if any
We noticed another site without the .princeton.edu extension getting a Sectigo renewal. Simon in OIT told us the pre-requisites:
We need access to email at one of these 5 addresses:
User story
We run
cicognara.org
on our load-balancers. However, because the site does not have the.princeton.edu
extension, we have been manually managing the cert for this site. We would like to manage the cert for cocognara.org the same way as all other certs for sites on the load-balancers.Acceptance criteria
Implementation notes, if any
We noticed another site without the
.princeton.edu
extension getting a Sectigo renewal. Simon in OIT told us the pre-requisites:We need access to email at one of these 5 addresses:
That's where Sectigo will send the correspondence about the new certificate.
The text was updated successfully, but these errors were encountered: