{"action":"opened","issue":{"url":"https://api.github.com/repos/jedireza/frame/issues/223","repository_url":"https://api.github.com/repos/jedireza/frame","labels_url":"https://api.github.com/repos/jedireza/frame/issues/223/labels{/name}","comments_url":"https://api.github.com/repos/jedireza/frame/issues/223/comments","events_url":"https://api.github.com/repos/jedireza/frame/issues/223/events","html_url":"https://github.com/jedireza/frame/issues/223","id":330011877,"node_id":"MDU6SXNzdWUzMzAwMTE4Nzc=","number":223,"title":"Switch framework default authentication to cookies/sessions instead of basic auth","user":{"login":"fishmongr","id":492460,"node_id":"MDQ6VXNlcjQ5MjQ2MA==","avatar_url":"https://avatars1.githubusercontent.com/u/492460?v=4","gravatar_id":"","url":"https://api.github.com/users/fishmongr","html_url":"https://github.com/fishmongr","followers_url":"https://api.github.com/users/fishmongr/followers","following_url":"https://api.github.com/users/fishmongr/following{/other_user}","gists_url":"https://api.github.com/users/fishmongr/gists{/gist_id}","starred_url":"https://api.github.com/users/fishmongr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fishmongr/subscriptions","organizations_url":"https://api.github.com/users/fishmongr/orgs","repos_url":"https://api.github.com/users/fishmongr/repos","events_url":"https://api.github.com/users/fishmongr/events{/privacy}","received_events_url":"https://api.github.com/users/fishmongr/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-06T20:01:42Z","updated_at":"2018-06-06T20:01:42Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"This is a killer Dev / User Portal framework boilerplate which is supposed to save folks time and automatically implement best practices. There aren't any production dev portals that use basic auth that i'm aware of, they all use cookie/sessions so I still think it would be a smart move to switch to that authentication by default, considering the Aqua version of this framework already defaults to it as well. \r\n\r\nAs a new developer on the framework the first thing I would do is hit the interactive signup/login flows through swagger docs and find they don't work as expected because they aren't creating and maintaining sessions like they appear to be designed to do.\r\n\r\nPreviously, documentation was the biggest barrier to entry, now that we have some solid Swagger docs, I think it's more of these little technical hurdles when rolling out a new platform with this boilerplate. Setting up cookie/session support is an unexpected chore. Just like setting up forgot/reset password flows or even \"abusive login attempt detection\" would be chore but is already wonderfully handled for you. \r\n\r\nThoughts? If agreeable we could just pull request Aqua's implementation which is working well for me."}}
{"actor":{"display_login":"fishmongr"}}