← 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
GlobalSign: Issuance of test certificate (pre-certificate) for EV SSL/QWAC with no EKU extension
GlobalSign: 4 Misissued certificates with invalid CN
GlobalSign: AT&T SSL certificates without the AIA extension
GlobalSign: EV certificate with wildcard domain in common name and SAN
GlobalSign: Misissuance of QWAC Certificates
GlobalSign: Wrong business category (Non Commercial Entity when should have been Private Organization)
Globalsign / AlphaSSL: CAA Mis-Issuance on mix of wildcard and non-wildcard DNS names in SAN
eMudhra emSign PKI Services : www Subdomain Inclusion in Certificate SAN via ACME Issuance Workflow