{"action":"opened","issue":{"url":"https://api.github.com/repos/magfest/sideboard/issues/34","repository_url":"https://api.github.com/repos/magfest/sideboard","labels_url":"https://api.github.com/repos/magfest/sideboard/issues/34/labels{/name}","comments_url":"https://api.github.com/repos/magfest/sideboard/issues/34/comments","events_url":"https://api.github.com/repos/magfest/sideboard/issues/34/events","html_url":"https://github.com/magfest/sideboard/issues/34","id":176995656,"number":34,"title":"/wsrpc should use the client cert username as the session username","user":{"login":"EliAndrewC","id":651592,"avatar_url":"https://avatars.githubusercontent.com/u/651592?v=3","gravatar_id":"","url":"https://api.github.com/users/EliAndrewC","html_url":"https://github.com/EliAndrewC","followers_url":"https://api.github.com/users/EliAndrewC/followers","following_url":"https://api.github.com/users/EliAndrewC/following{/other_user}","gists_url":"https://api.github.com/users/EliAndrewC/gists{/gist_id}","starred_url":"https://api.github.com/users/EliAndrewC/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/EliAndrewC/subscriptions","organizations_url":"https://api.github.com/users/EliAndrewC/orgs","repos_url":"https://api.github.com/users/EliAndrewC/repos","events_url":"https://api.github.com/users/EliAndrewC/events{/privacy}","received_events_url":"https://api.github.com/users/EliAndrewC/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-14T19:18:13Z","updated_at":"2016-09-14T19:18:13Z","closed_at":null,"body":"Moved here from the original (now private) issue tracker.\r\n\r\n``/wsrpc`` is assumed to be client-cert protected. Currently the \"username\" we log for those requests is ``rpc``, but it would be nice to use this as the default, but if a client cert exists with a non-empty CN then we'd use that as the username.\r\n\r\nThis currently only matters for logging, but this will be relevant when we expose different authentication and authorization methods.  In particular, it would be nice to restrict some API calls to only be callable by certain clients."}}
{"actor":{"display_login":"EliAndrewC"}}