{"action":"created","issue":{"url":"https://api.github.com/repos/GSA/jenkins-deploy/issues/2","repository_url":"https://api.github.com/repos/GSA/jenkins-deploy","labels_url":"https://api.github.com/repos/GSA/jenkins-deploy/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/GSA/jenkins-deploy/issues/2/comments","events_url":"https://api.github.com/repos/GSA/jenkins-deploy/issues/2/events","html_url":"https://github.com/GSA/jenkins-deploy/issues/2","id":226183550,"number":2,"title":"use GitHub for authentication","user":{"login":"afeld","id":86842,"avatar_url":"https://avatars3.githubusercontent.com/u/86842?v=3","gravatar_id":"","url":"https://api.github.com/users/afeld","html_url":"https://github.com/afeld","followers_url":"https://api.github.com/users/afeld/followers","following_url":"https://api.github.com/users/afeld/following{/other_user}","gists_url":"https://api.github.com/users/afeld/gists{/gist_id}","starred_url":"https://api.github.com/users/afeld/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/afeld/subscriptions","organizations_url":"https://api.github.com/users/afeld/orgs","repos_url":"https://api.github.com/users/afeld/repos","events_url":"https://api.github.com/users/afeld/events{/privacy}","received_events_url":"https://api.github.com/users/afeld/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2017-05-04T05:53:38Z","updated_at":"2017-05-05T19:44:37Z","closed_at":null,"body":"* https://plugins.jenkins.io/github-oauth\r\n* https://wiki.jenkins-ci.org/display/JENKINS/Matrix-based+security\r\n* https://plugins.jenkins.io/role-strategy\r\n\r\nLikely makes sense to address authorization as a separate issue."},"comment":{"url":"https://api.github.com/repos/GSA/jenkins-deploy/issues/comments/299558358","html_url":"https://github.com/GSA/jenkins-deploy/issues/2#issuecomment-299558358","issue_url":"https://api.github.com/repos/GSA/jenkins-deploy/issues/2","id":299558358,"user":{"login":"afeld","id":86842,"avatar_url":"https://avatars3.githubusercontent.com/u/86842?v=3","gravatar_id":"","url":"https://api.github.com/users/afeld","html_url":"https://github.com/afeld","followers_url":"https://api.github.com/users/afeld/followers","following_url":"https://api.github.com/users/afeld/following{/other_user}","gists_url":"https://api.github.com/users/afeld/gists{/gist_id}","starred_url":"https://api.github.com/users/afeld/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/afeld/subscriptions","organizations_url":"https://api.github.com/users/afeld/orgs","repos_url":"https://api.github.com/users/afeld/repos","events_url":"https://api.github.com/users/afeld/events{/privacy}","received_events_url":"https://api.github.com/users/afeld/received_events","type":"User","site_admin":false},"created_at":"2017-05-05T19:44:37Z","updated_at":"2017-05-05T19:44:37Z","body":"> Would you be creating a new team in Github and restricting access to Jenkins based on membership to that team? or would you be essentially giving the whole team (current members) the same rights to login and operate within Jenkins?\r\n\r\nThe latter. I was thinking we'd give admin (or at least write) access to the [d2d](https://github.com/orgs/GSA/teams/d2d) team, and maybe read-only access to the [d2d-read-only](https://github.com/orgs/GSA/teams/d2d-read-only) team.\r\n\r\n> Can you give me a run down on how the process would look from your side?\r\n\r\nI'll get a demo together 😁 Should be fairly easy to set up."}}
{"actor":{"display_login":"afeld"}}