← GlobalSign nv-sa cases
Bugzilla #1048045
Certificate Misissuance
GlobalSign Partner: No SAN
RESOLVED
GlobalSign nv-sa
AI Summary
This case addresses a misissuance issue where a certificate issued by GlobalSign's Partner Program did not include the Subject Alternative Name (SAN) extension, which is required by CA/B Forum Baseline Requirements. GlobalSign acknowledged the oversight, explaining that the certificate was part of an older program that has since been updated to ensure compliance. The issue has been resolved as the necessary corrective actions have been implemented, and all new certificates now include SANs.
Chronology
- Case created regarding missing SAN in certificate.
- GlobalSign provided details on the certificate issuance and compliance actions.
Participants
him@ian.sh
Steve Roylance
External References
Similar Local Cases
Digicert: Failure to include CPS URI in 1 certificate
Apple: EV TLS pre-certificates issued without EKU extension
Trustis: Certificate not version 3
Let's Encrypt: CAA Misissuances
DigiCert / Swiss Government: CommonName not in SANs
DigiCert: DigiCert issued cert with CN too long
DigiCert: Verizon mis-issued test certificates
DigiCert: CAA processing during network disruption