Closed iamdanfox closed 9 years ago
Should work with pure-web: https://developer.github.com/v3/oauth/#web-application-flow
code
parameter) - this can be exchanged for an Access Token (this is actually useful)Actually scratch that - the client_secret
shouldn't be exposed to the world ... maybe hide inside a little heroku node app?
https://ghupdate.herokuapp.com/ is in place, published from the heroku
branch
Now just need to implement 'Step 1' on the frontend.
Think there may be an origin problem (initial redirect comes from a different location to the access_token request)
BOOM it works. access_token
successfully acquired on the frontend. Turns out qwest wasn't passing the argument correctly.
Re-implement this in the reflux world.
Hopefully this will get round some of the auth problems