-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relax minimum subject DN field values for trustedIdentities to not include state/province (S/ST) #293
Comments
@gokarnm @priteshbandi @shizhMSFT @Two-Hearts Would you mind taking a look at this issue? |
Hi Ian - |
CN and O field values are commonly the same values, but there are many cases where a legal tradename or "dba" (doing business as) name can be placed in the O field while the CN value remains to the be legal organization or individual name. That said, we could allow for the minimum to exclude CN as @priteshbandi recommends. |
@priteshbandi I checked the section |
The "commonName" (CN) field is required when issuing certificates. For TLS/SSL certificates, the commonName is usually set to the domain name that the certificate will be used for. For code signing certificates, the commonName is often set to the name of the organization. However, for the purposes of signature verification, IMO the commonName should be optional as "Organization" (O) DN is already a mandatory component of trusted identity. Also, we have C, ST, O as mandatory field to uniquely identify an organization. |
Currently in the Trust Store and Trust Policy Specification in the Trusted Identities Constraints section there is a minimum field requirement on x.509 cert subject DN values stated as:
"Each identity in identities list MUST contain country (C), state or province (ST), and organization (O) RDNs. All other RDNs are optional. The minimal possible value is
x509.subject: C=${country}, ST=${state}, O={organization}
,"Not all identities will have a state/province value unless the identity is in the US or Canada, so the
ST
orS
value need to NOT be required. The minimum subject DN fields should beCN=
,O=
,L=
,C=
. Signing certs commonly use these values as the minimum for subject DN.The text was updated successfully, but these errors were encountered: