{"action":"created","issue":{"url":"https://api.github.com/repos/letsencrypt/boulder/issues/98","labels_url":"https://api.github.com/repos/letsencrypt/boulder/issues/98/labels{/name}","comments_url":"https://api.github.com/repos/letsencrypt/boulder/issues/98/comments","events_url":"https://api.github.com/repos/letsencrypt/boulder/issues/98/events","html_url":"https://github.com/letsencrypt/boulder/issues/98","id":68831530,"number":98,"title":"Additional SANs in CSR are ignored","user":{"login":"rufoa","id":1864616,"avatar_url":"https://avatars.githubusercontent.com/u/1864616?v=3","gravatar_id":"","url":"https://api.github.com/users/rufoa","html_url":"https://github.com/rufoa","followers_url":"https://api.github.com/users/rufoa/followers","following_url":"https://api.github.com/users/rufoa/following{/other_user}","gists_url":"https://api.github.com/users/rufoa/gists{/gist_id}","starred_url":"https://api.github.com/users/rufoa/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rufoa/subscriptions","organizations_url":"https://api.github.com/users/rufoa/orgs","repos_url":"https://api.github.com/users/rufoa/repos","events_url":"https://api.github.com/users/rufoa/events{/privacy}","received_events_url":"https://api.github.com/users/rufoa/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-04-16T02:45:08Z","updated_at":"2015-04-16T10:22:24Z","closed_at":null,"body":"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.\r\n\r\ne.g. I request a cert for \"example.org,www.example.org\"\r\nThe CSR has CN=example.org, SAN={example.org,www.example.org}\r\n\r\nExpected cert:\r\nCN=example.org, SAN={example.org,www.example.org}\r\n\r\nActual issued cert:\r\nCN=example.org, SAN={example.org}\r\n\r\nI can't see any obvious error in certificate-authority.go - is this a bug upstream in CFSSL perhaps?"},"comment":{"url":"https://api.github.com/repos/letsencrypt/boulder/issues/comments/93701923","html_url":"https://github.com/letsencrypt/boulder/issues/98#issuecomment-93701923","issue_url":"https://api.github.com/repos/letsencrypt/boulder/issues/98","id":93701923,"user":{"login":"jdkasten","id":1581662,"avatar_url":"https://avatars.githubusercontent.com/u/1581662?v=3","gravatar_id":"","url":"https://api.github.com/users/jdkasten","html_url":"https://github.com/jdkasten","followers_url":"https://api.github.com/users/jdkasten/followers","following_url":"https://api.github.com/users/jdkasten/following{/other_user}","gists_url":"https://api.github.com/users/jdkasten/gists{/gist_id}","starred_url":"https://api.github.com/users/jdkasten/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jdkasten/subscriptions","organizations_url":"https://api.github.com/users/jdkasten/orgs","repos_url":"https://api.github.com/users/jdkasten/repos","events_url":"https://api.github.com/users/jdkasten/events{/privacy}","received_events_url":"https://api.github.com/users/jdkasten/received_events","type":"User","site_admin":false},"created_at":"2015-04-16T10:22:24Z","updated_at":"2015-04-16T10:22:24Z","body":"Unless you are using the boulder branch of the LE client... the client\nisn't communicating with Boulder.\n\nThe master branch is still using v00 of the protocol and working with the\nnode-acme server that doesn't support multiple hostnames.\n\nI am currently cleaning up the boulder branch, adding account\ninfrastructure to go with the registration, and writing test cases.\nHopefully I can get a pull-request to master by tomorrow.\n\nI did test the boulder branch with multiple hostnames though and it appears\nto work.\n\nSorry about the confusion.\nJames\n\nOn Wed, Apr 15, 2015 at 7:45 PM, rufoa <notifications@github.com> wrote:\n\n> When I use the LE client to request a certificate for more than one\n> hostname, only the first one seems to be included in the certificate. All\n> additional hostnames seem to be ignored. However, the CSR which is\n> generated appears to be correct - the problem seems to be occurring at the\n> boulder end.\n>\n> e.g. I request a cert for \"example.org,www.example.org\"\n> The CSR has CN=example.org, SAN={example.org,www.example.org}\n>\n> Expected cert:\n> CN=example.org, SAN={example.org,www.example.org}\n>\n> Actual issued cert:\n> CN=example.org, SAN={example.org}\n>\n> I can't see any obvious error in certificate-authority.go - is this a bug\n> upstream in CFSSL perhaps?\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/letsencrypt/boulder/issues/98>.\n>\n"}}