-
-
Notifications
You must be signed in to change notification settings - Fork 606
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
Additional SANs in CSR are ignored #98
Comments
Unless you are using the boulder branch of the LE client... the client The master branch is still using v00 of the protocol and working with the I am currently cleaning up the boulder branch, adding account I did test the boulder branch with multiple hostnames though and it appears Sorry about the confusion. On Wed, Apr 15, 2015 at 7:45 PM, rufoa notifications@github.com wrote:
|
Ah that explains it! Thanks and sorry for the misunderstanding. |
When I use the LE client to request a certificate for more than one hostname, only the first one seems to be included in the certificate. All additional hostnames seem to be ignored. However, the CSR which is generated appears to be correct - the problem seems to be occurring at the boulder end.
e.g. I request a cert for "example.org,www.example.org"
The CSR has CN=example.org, SAN={example.org,www.example.org}
Expected cert:
CN=example.org, SAN={example.org,www.example.org}
Actual issued cert:
CN=example.org, SAN={example.org}
I can't see any obvious error in certificate-authority.go - is this a bug upstream in CFSSL perhaps?
The text was updated successfully, but these errors were encountered: