{"action":"created","issue":{"url":"https://api.github.com/repos/heroku/heroku-cli/issues/45","labels_url":"https://api.github.com/repos/heroku/heroku-cli/issues/45/labels{/name}","comments_url":"https://api.github.com/repos/heroku/heroku-cli/issues/45/comments","events_url":"https://api.github.com/repos/heroku/heroku-cli/issues/45/events","html_url":"https://github.com/heroku/heroku-cli/issues/45","id":93588100,"number":45,"title":"login flow should be via the web","user":{"login":"dpiddy","id":2182,"avatar_url":"https://avatars.githubusercontent.com/u/2182?v=3","gravatar_id":"","url":"https://api.github.com/users/dpiddy","html_url":"https://github.com/dpiddy","followers_url":"https://api.github.com/users/dpiddy/followers","following_url":"https://api.github.com/users/dpiddy/following{/other_user}","gists_url":"https://api.github.com/users/dpiddy/gists{/gist_id}","starred_url":"https://api.github.com/users/dpiddy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dpiddy/subscriptions","organizations_url":"https://api.github.com/users/dpiddy/orgs","repos_url":"https://api.github.com/users/dpiddy/repos","events_url":"https://api.github.com/users/dpiddy/events{/privacy}","received_events_url":"https://api.github.com/users/dpiddy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-07-07T17:46:51Z","updated_at":"2015-11-10T23:45:29Z","closed_at":null,"body":"Currently `heroku login` prompts for email and password. To do that, I need to flip to my password manager and get at least my password, if not my email as well for convenience.\r\n\r\nIt would be very nice if instead `heroku login` did a normal web-based OAuth flow so, if I get prompted for email and password by id.heroku.com or similar, I can just use my password manager as I do for the web normally."},"comment":{"url":"https://api.github.com/repos/heroku/heroku-cli/issues/comments/155604343","html_url":"https://github.com/heroku/heroku-cli/issues/45#issuecomment-155604343","issue_url":"https://api.github.com/repos/heroku/heroku-cli/issues/45","id":155604343,"user":{"login":"naaman","id":143326,"avatar_url":"https://avatars.githubusercontent.com/u/143326?v=3","gravatar_id":"","url":"https://api.github.com/users/naaman","html_url":"https://github.com/naaman","followers_url":"https://api.github.com/users/naaman/followers","following_url":"https://api.github.com/users/naaman/following{/other_user}","gists_url":"https://api.github.com/users/naaman/gists{/gist_id}","starred_url":"https://api.github.com/users/naaman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/naaman/subscriptions","organizations_url":"https://api.github.com/users/naaman/orgs","repos_url":"https://api.github.com/users/naaman/repos","events_url":"https://api.github.com/users/naaman/events{/privacy}","received_events_url":"https://api.github.com/users/naaman/received_events","type":"User","site_admin":false},"created_at":"2015-11-10T23:45:29Z","updated_at":"2015-11-10T23:45:29Z","body":"@friism I'm not sure how they're avoiding a browser. They're opening a local webserver and running an instance of a browser. The App Harbor approach is just showing a way to avoid a centrally running web-based callback by running a local webserver. The harder problem is eliminating the handling of usernames and passwords AND eliminating the need for a browser.\r\n\r\n@dpiddy there are also headless flows where a user _may not_ have access to a browser. e.g. SSH sessions.\r\n\r\nThat said, I think defaulting to a web-based login flow would be ideal. Overall, logging into my CLI via a browser works smoothly with password managers and allows SSO users to seamlessly login. As a fallback, an option to login interactively via a flag seems like a reasonable way to allow headless users to login. @dickeyxxx recently proposed `heroku login --interactive` for this approach and `heroku login` defaults to popping open a web browser."}}