{"action":"created","issue":{"url":"https://api.github.com/repos/hashicorp/vault/issues/593","labels_url":"https://api.github.com/repos/hashicorp/vault/issues/593/labels{/name}","comments_url":"https://api.github.com/repos/hashicorp/vault/issues/593/comments","events_url":"https://api.github.com/repos/hashicorp/vault/issues/593/events","html_url":"https://github.com/hashicorp/vault/issues/593","id":105104419,"number":593,"title":"Configurable Subject Alternative Names","user":{"login":"theonewolf","id":522248,"avatar_url":"https://avatars.githubusercontent.com/u/522248?v=3","gravatar_id":"","url":"https://api.github.com/users/theonewolf","html_url":"https://github.com/theonewolf","followers_url":"https://api.github.com/users/theonewolf/followers","following_url":"https://api.github.com/users/theonewolf/following{/other_user}","gists_url":"https://api.github.com/users/theonewolf/gists{/gist_id}","starred_url":"https://api.github.com/users/theonewolf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/theonewolf/subscriptions","organizations_url":"https://api.github.com/users/theonewolf/orgs","repos_url":"https://api.github.com/users/theonewolf/repos","events_url":"https://api.github.com/users/theonewolf/events{/privacy}","received_events_url":"https://api.github.com/users/theonewolf/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-09-06T17:06:13Z","updated_at":"2015-09-08T14:10:03Z","closed_at":"2015-09-06T19:05:37Z","body":"I'd like to comply with x509 specification better by allowing other types of Subject Alternative Name.\r\n\r\nCurrently the design in Vault is hard-coded to only let in DNS names *I think*.\r\n\r\nI'm using the subject name as a form of node identifier (could be DNS based), and the alternative names as listing service and group identifiers (not necessarily each one having its own DNS name).\r\n\r\nIn my actual use case, the common name is a UUID as are all the alternative names.  In this manner I can use these PKI certificates to identify arbitrary entities not necessarily having DNS names labeling them.  For example, many processes on a host can be identified with a unique certificate without requiring every process to also have a unique DNS record."},"comment":{"url":"https://api.github.com/repos/hashicorp/vault/issues/comments/138570833","html_url":"https://github.com/hashicorp/vault/issues/593#issuecomment-138570833","issue_url":"https://api.github.com/repos/hashicorp/vault/issues/593","id":138570833,"user":{"login":"theonewolf","id":522248,"avatar_url":"https://avatars.githubusercontent.com/u/522248?v=3","gravatar_id":"","url":"https://api.github.com/users/theonewolf","html_url":"https://github.com/theonewolf","followers_url":"https://api.github.com/users/theonewolf/followers","following_url":"https://api.github.com/users/theonewolf/following{/other_user}","gists_url":"https://api.github.com/users/theonewolf/gists{/gist_id}","starred_url":"https://api.github.com/users/theonewolf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/theonewolf/subscriptions","organizations_url":"https://api.github.com/users/theonewolf/orgs","repos_url":"https://api.github.com/users/theonewolf/repos","events_url":"https://api.github.com/users/theonewolf/events{/privacy}","received_events_url":"https://api.github.com/users/theonewolf/received_events","type":"User","site_admin":false},"created_at":"2015-09-08T14:10:03Z","updated_at":"2015-09-08T14:10:03Z","body":"Yeah, that's fine.  I'm just happy to have a centralized, PKI tool that I enjoy working with."}}