Closed Bug 1129522 Opened 9 years ago Closed 9 years ago

SSL needed super fast for call.mozillafoundation.org

Categories

(Infrastructure & Operations :: SSL Certificates, task, P1)

Product:
Infrastructure & Operations
Component:
SSL Certificates
Platform:
x86
macOS
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Due Date:

People

(Reporter: johns, Assigned: gozer)

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/415] ) 

Hi, sorry for the rush!  This is launching today, we hope.

Tech Email:hostmaster@mozilla.com is getting an email for Extended Validation which we need to immediatley approve, please.

Then, please quickly approve the cert provisioning in digicert for call.mozillafoundation.org (I just subbed that request on digicert)
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/415]
Assignee: server-ops-webops → gozer
Status: NEW → ASSIGNED
Just curious about how this could become so urgent so quickly? Wasn't the need for an SSL certificate planned ahead?

Just want to understand the process that lead to this.

Working on pushing it through digicert.
The naming part was completed today, thus the issue.  Sorry Gozer, I know that sucks, my apologies.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
And its already through Digicert, I have it actually up in Cloudfront already.  Sorry again for the mad rush here, I wasn't a fan either.  Naming is always somehow the hardest thing we have to do.
(In reply to JP Schneider :jp from comment #3)
> And its already through Digicert, I have it actually up in Cloudfront
> already.  Sorry again for the mad rush here, I wasn't a fan either.  Naming
> is always somehow the hardest thing we have to do.

Yes, but if we are going to use a different name in the end, then this ssl cert, associated DNS work, etc, should be reverted, no?

Or is the stuff in bug 1129672 a different (but related) issue ?
"(In reply to Philippe M. Chiasson (:gozer) from comment #4)

> 
> Yes, but if we are going to use a different name in the end, then this ssl
> cert, associated DNS work, etc, should be reverted, no?
> 

Yessir.  We already bought that cert, so not sure if we can return it or anything, but if so, sure.

> Or is the stuff in bug 1129672 a different (but related) issue ?
bug 1129672 is the same effort, and since we changed the desired DNS from call.mozillafoundation.org to call.mozilla.com, that bug will get me the cert to put up on cloudfront.
bug 1129674 is for the associated DNS change as well.
You need to log in before you can comment on or make changes to this bug.