Skip to main content

Timeline for Login screen without web browser

Current License: CC BY-SA 3.0

9 events
when toggle format what by license comment
Apr 13, 2017 at 12:25 history edited CommunityBot
replaced http://stackapps.com/ with https://stackapps.com/
Oct 30, 2015 at 20:59 comment added Mitch HA! Ok, will give it a try and come back with my results. :)
Oct 30, 2015 at 20:56 comment added Brock Adams I haven't done it since OAuth(1) (All my current apps are browser based), but it can't be too hard, as people do it all day. Suggest you grab an OAuth2 API library for Google or Facebook or similar. I know they have them for the most popular languages... Make a test app for one of those sites that logs in... Then adjust the app to use the same techniques for the SE API... Then come back here and show how you did it... {magic happens here}... Profit!
Oct 30, 2015 at 20:52 comment added Mitch Ok, great, so it is possible. It sounds kind of difficult though. How much work are talking about, to handle "iframes and redirects"? How do I know what input fields I need to display so that the user can enter their details? Is this where the OAuth API would come in? I don't really know where to begin. :)
Oct 30, 2015 at 20:47 comment added Brock Adams Your app must be able to: (1) make HTTPS GET requests to stackexchange.com, (2) parse the results, and (3) follow redirects. ... IIRC, if your app does not display the stackexchange.com/oauth/dialog page in a browser window, then it must be smart enough to act as a man-in-the-middle for the user's interaction with that page (plus any relevant iframes and redirects).
Oct 30, 2015 at 20:38 comment added Brock Adams Related: OAuth procedure for standalone user?.
Oct 30, 2015 at 20:36 history edited Brock Adams
edited tags
Oct 30, 2015 at 19:48 review First posts
Oct 30, 2015 at 20:36
Oct 30, 2015 at 19:37 history asked Mitch CC BY-SA 3.0