Cert manager requires fields that aren't necessary
Attempting to generate a CA or certificate via the cert management tool in the web GUI yields the following error:
"The field Distinguished name Email Address is required."
The emailAddress field is not required in any X.509v3-compliant certificate, unless that certificate is intended for use as an email signing certificate. According to RFC 5280, only a certificate intended to authenticate an email address (such as an email signing certificate) should include an email address at all, and even then, it must be done as an RFC822Name entry under the Subject Alternative Name extension.
Conforming implementations generating new certificates with electronic mail addresses MUST use the rfc822Name in the subject alternative name extension (Section 220.127.116.11) to describe such identities. Simultaneous inclusion of the emailAddress attribute in the subject distinguished name to support legacy implementations is deprecated but permitted.
In fact, the ONLY attribute that is mandatory for the DistinguishedName field in a certificate is the CommonName attribute. All other attributes should be made optional in the web GUI.
Updated by Justin Coffman over 5 years ago
Clarifying that last line:
RFC 3280 defines how the subject of a certificate or CA must be specified. Ideally, the web GUI would include logic to handle an RFC-compliant combination of cases, but reviewing section 18.104.22.168 gives the idea that this may be overly complicated. More reasonable would be to make the CommonName attribute required, and all others optional.