Closed Bug 1478480 Opened 3 years ago Closed 3 years ago

Enable GlobalSign Root CA - R6 for EV in PSM


(Core :: Security: PSM, enhancement, P1)

63 Branch



Tracking Status
firefox63 --- wontfix
firefox64 --- fixed


(Reporter: kwilson, Assigned: keeler)



(Whiteboard: [psm-assigned])


(1 file)

Per bug #1390803 the request from GlobalSign has been approved to enable the following root certificate for EV use. Please make the corresponding changes to PSM.

Friendly Name: GlobalSign Root CA - R6
SHA-1 Fingerprint: 8094640EB5A7A1CA119C1FDDD59F810263A7FBD1
SHA-256 Fingerprint: 2CABEAFE37D06CA22ABA7391C0033D25982952C453647349763A3AB5AD6CCF69
EV Policy OID:
Test URL:
Assignee: nobody → dkeeler
Whiteboard: [psm-assigned]

Please confirm that we should use the GlobalSign EV OID ( instead of the CAB Forum EV OID ( for enabling EV treatment for this "GlobalSign Root CA - R6" root.

Dana ran into a problem when adding EV treatment for GlobalSign Root CA - R6. If we want this root to be authoritative for the EV Policy OID, any end-entities GlobalSign issues will have to list that OID first -- which is not what we're seeing with the test site 
If the certificate verifier finds the GlobalSign EV OID ( first, it'll try to use that OID since we already have GlobalSign roots that are authoritative for it. That won't work of we've used for this root -- it'll fall back to DV.
So we believe we should make this root authoritative for the GlobalSign EV OID.
Flags: needinfo?(julie.olson)
It sounds like there is another option... to change all GlobalSign roots to use the CABF EV OID in Firefox. However, this will only work if all existing GlobalSign EV certs contain the CABF EV OID (in addition to the GlobalSign EV OID).
Hi Kathleen,

All of our active SSL EV certificates have both the GlobalSign and CA/BF OID. We will make sure to flip the OID order moving forward so the CA/BF one goes first.

Flags: needinfo?(julie.olson)
Julie, Do all of GlobalSign's EV intermediate certificates have the CABF EV Policy OID or the AnyPolicy OID?
If yes, then when we add EV treatment for this root, we will change all GlobalSign occurrences in ExtendedValidation.cpp to use the CABF EV OID.
Hi Kathleen,

Sorry, yes, all of those certificates have the CABF EV Policy OID.

This patch also switches all GlobalSign EV roots to using the CA/Browser Forum
EV policy OID.
Pushed by
enable GlobalSign Root CA - R6 for EV in PSM r=franziskus
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Julie, this change is now available in Firefox Nightly. I have tested and verified EV treatment for a couple test websites, and it looks good. Please perform additional testing.

You need to log in before you can comment on or make changes to this bug.