{"action":"created","issue":{"url":"https://api.github.com/repos/cloudfoundry/bosh/issues/1329","repository_url":"https://api.github.com/repos/cloudfoundry/bosh","labels_url":"https://api.github.com/repos/cloudfoundry/bosh/issues/1329/labels{/name}","comments_url":"https://api.github.com/repos/cloudfoundry/bosh/issues/1329/comments","events_url":"https://api.github.com/repos/cloudfoundry/bosh/issues/1329/events","html_url":"https://github.com/cloudfoundry/bosh/issues/1329","id":163399529,"number":1329,"title":"Bosh team admins","user":{"login":"ChrisMcGowan","id":12498453,"avatar_url":"https://avatars.githubusercontent.com/u/12498453?v=3","gravatar_id":"","url":"https://api.github.com/users/ChrisMcGowan","html_url":"https://github.com/ChrisMcGowan","followers_url":"https://api.github.com/users/ChrisMcGowan/followers","following_url":"https://api.github.com/users/ChrisMcGowan/following{/other_user}","gists_url":"https://api.github.com/users/ChrisMcGowan/gists{/gist_id}","starred_url":"https://api.github.com/users/ChrisMcGowan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ChrisMcGowan/subscriptions","organizations_url":"https://api.github.com/users/ChrisMcGowan/orgs","repos_url":"https://api.github.com/users/ChrisMcGowan/repos","events_url":"https://api.github.com/users/ChrisMcGowan/events{/privacy}","received_events_url":"https://api.github.com/users/ChrisMcGowan/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/cloudfoundry/bosh/labels/problem","name":"problem","color":"eb6420"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-07-01T13:48:52Z","updated_at":"2016-07-08T12:56:44Z","closed_at":null,"body":"I have been experimenting with bosh uaa integration and bosh team admins and fould an interesting issue.  I can define users to uaa and add them to team groups like `bosh.teams.team1.admin` which allows the following expected behaviors -  `bosh target`, `bosh login`, and `bosh deploy` but not `bosh ssh` on their deployments.  Turns out I had to add those users to `bosh.read` in order to be able to use `bosh ssh`.  Is this normal behavior for bosh teams?  I presumed that a user with a `*.admin` role would already have read permissions.   Thanks\r\n"},"comment":{"url":"https://api.github.com/repos/cloudfoundry/bosh/issues/comments/231352326","html_url":"https://github.com/cloudfoundry/bosh/issues/1329#issuecomment-231352326","issue_url":"https://api.github.com/repos/cloudfoundry/bosh/issues/1329","id":231352326,"user":{"login":"ChrisMcGowan","id":12498453,"avatar_url":"https://avatars.githubusercontent.com/u/12498453?v=3","gravatar_id":"","url":"https://api.github.com/users/ChrisMcGowan","html_url":"https://github.com/ChrisMcGowan","followers_url":"https://api.github.com/users/ChrisMcGowan/followers","following_url":"https://api.github.com/users/ChrisMcGowan/following{/other_user}","gists_url":"https://api.github.com/users/ChrisMcGowan/gists{/gist_id}","starred_url":"https://api.github.com/users/ChrisMcGowan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ChrisMcGowan/subscriptions","organizations_url":"https://api.github.com/users/ChrisMcGowan/orgs","repos_url":"https://api.github.com/users/ChrisMcGowan/repos","events_url":"https://api.github.com/users/ChrisMcGowan/events{/privacy}","received_events_url":"https://api.github.com/users/ChrisMcGowan/received_events","type":"User","site_admin":false},"created_at":"2016-07-08T12:56:44Z","updated_at":"2016-07-08T12:56:44Z","body":"I started with a fresh director deployment using `256.2` and did the initial `team1` deployment  while on that release of the director and received the error in question.  I then upgraded the director at that time to `257.1`, logged out and back into the director and tried `bosh ssh` again and same result.  This was when I added the scope `bosh.read` to the test `team11` user.\r\n\r\n"}}
{"actor":{"display_login":"ChrisMcGowan"}}