{"action":"closed","issue":{"url":"https://api.github.com/repos/CartoDB/cartodb/issues/8970","repository_url":"https://api.github.com/repos/CartoDB/cartodb","labels_url":"https://api.github.com/repos/CartoDB/cartodb/issues/8970/labels{/name}","comments_url":"https://api.github.com/repos/CartoDB/cartodb/issues/8970/comments","events_url":"https://api.github.com/repos/CartoDB/cartodb/issues/8970/events","html_url":"https://github.com/CartoDB/cartodb/issues/8970","id":166285833,"number":8970,"title":"Limit scope for API keys","user":{"login":"jaakla","id":5609650,"avatar_url":"https://avatars.githubusercontent.com/u/5609650?v=3","gravatar_id":"","url":"https://api.github.com/users/jaakla","html_url":"https://github.com/jaakla","followers_url":"https://api.github.com/users/jaakla/followers","following_url":"https://api.github.com/users/jaakla/following{/other_user}","gists_url":"https://api.github.com/users/jaakla/gists{/gist_id}","starred_url":"https://api.github.com/users/jaakla/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jaakla/subscriptions","organizations_url":"https://api.github.com/users/jaakla/orgs","repos_url":"https://api.github.com/users/jaakla/repos","events_url":"https://api.github.com/users/jaakla/events{/privacy}","received_events_url":"https://api.github.com/users/jaakla/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/CartoDB/cartodb/labels/enhancement","name":"enhancement","color":"84b6eb"},{"url":"https://api.github.com/repos/CartoDB/cartodb/labels/feature","name":"feature","color":"fbca04"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-07-19T09:24:38Z","updated_at":"2016-07-19T09:28:13Z","closed_at":"2016-07-19T09:28:13Z","body":"First, user should be able to generate many API keys.\r\n\r\nFor new keys enable limiting scope of API keys. Existing key is with \"global\" permission which should never be used in public client (web/mobile), but new keys should have scope definition, and API should take this into account. Possible scopes could be grouped to two, something like: \r\n\r\na) safe - cannot damage data, can only damage budget: map api (anonymous, initiate named), read base map tiles, sql select, data services\r\nb) unsafe - can damage data also: manage named maps, sql ddl, sql update/delete, import api\r\n"}}
{"actor":{"display_login":"jaakla"}}