{"action":"opened","issue":{"url":"https://api.github.com/repos/timeravel/timeravel/issues/29","repository_url":"https://api.github.com/repos/timeravel/timeravel","labels_url":"https://api.github.com/repos/timeravel/timeravel/issues/29/labels{/name}","comments_url":"https://api.github.com/repos/timeravel/timeravel/issues/29/comments","events_url":"https://api.github.com/repos/timeravel/timeravel/issues/29/events","html_url":"https://github.com/timeravel/timeravel/issues/29","id":273731700,"number":29,"title":"Elaborate the technical and functional needs for authentication and authorization in timeravel","user":{"login":"KacAmo","id":8656347,"avatar_url":"https://avatars2.githubusercontent.com/u/8656347?v=4","gravatar_id":"","url":"https://api.github.com/users/KacAmo","html_url":"https://github.com/KacAmo","followers_url":"https://api.github.com/users/KacAmo/followers","following_url":"https://api.github.com/users/KacAmo/following{/other_user}","gists_url":"https://api.github.com/users/KacAmo/gists{/gist_id}","starred_url":"https://api.github.com/users/KacAmo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/KacAmo/subscriptions","organizations_url":"https://api.github.com/users/KacAmo/orgs","repos_url":"https://api.github.com/users/KacAmo/repos","events_url":"https://api.github.com/users/KacAmo/events{/privacy}","received_events_url":"https://api.github.com/users/KacAmo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-11-14T10:01:58Z","updated_at":"2017-11-14T10:01:58Z","closed_at":null,"author_association":"NONE","body":"# Description\n\nElaborate the technical and functional needs for authentication and authorization in timeravel. Check OpenId Connect and Oauth2, differences and commonalities and assess the needs of timeravel in terms of access to google apis and make suggestions for technology choices for authentication/authorization to be used in timeravel while justifying the rational behind these choices\n\n# Acceptance Criteria\n\n1. Markdown file \"docs/product-technology.md.md\" has been extended to answer the concerns mentioned above.\n\n# Attachments\n\nOriginal e-mail from Gunther: I thought it makes sense that you take a look at the login as it is done with the test Editor for timeravel. There OpenID Connect is used to handle a google login. This solution you can indeed with the in Compare Time Ravel times and put together the differences times (Pros / cons, integration with other Google services, etc.). \n\nThe goal is to get a clear picture of what we want to use exactly at Time Ravel. \n\nAs part of this can you also check out the topic of token refreshing (not yet implemented for the test editor), and accordingly also the token storage handling (security concerns), etc."}}
{"actor":{"display_login":"KacAmo"}}