kubla.mozilla.com should use *.mozilla.com wildcard SSL certificate

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
RESOLVED FIXED
9 years ago
3 years ago

People

(Reporter: reed, Assigned: zandr)

Tracking

Details

(URL)

(Reporter)

Description

9 years ago
kubla.mozilla.com uses an invalid security certificate.

The certificate is only valid for *.stage.mozilla.com

Comment 1

9 years ago
Wil, is this required?  Or will a Mozilla signed certificate suffice?  What are your requirements?
Summary: kubla.mozilla.com should use *.mozilla.com wildcard SSL certificate → kubla.mozilla.com should use kubla.mozilla.com SSL certificate
(Reporter)

Comment 2

9 years ago
People outside of MoCo use this (localizers, for instance). Why can't we just use the wildcard cert for this instead of trying to force a MoCo cert on people? This is definitely a regression, too.

Comment 3

9 years ago
I read kubla as khan so my bad.
(Reporter)

Updated

9 years ago
Summary: kubla.mozilla.com should use kubla.mozilla.com SSL certificate → kubla.mozilla.com should use *.mozilla.com wildcard SSL certificate
(Assignee)

Updated

9 years ago
Assignee: server-ops → zandr
Status: NEW → ASSIGNED
(Assignee)

Comment 4

9 years ago
*.mozilla.com installed on the netscaler. Tested, no warnings, http://kubla.mozilla.com
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.