2 replies to this topic

[Martin Harvey]

I had someone using my Android app and they fell at the first hurdle. They could not authorise the app via the evernote oAuth mechanism. They were presented with the browser and the normal evernote sign in screen... when they signed in, nothing happened - ie the browswer just stayed on the same page.

I played around with it and discovered they had disabled cookie's in the browser. When I turned them on, the authorisation worked as expected.

I haven't been able to find anything about this behaviour. However, was wondering if cookies are required for oAuth to work (on Android) or was it some kind of glitch?

If cookies are required I was thinking I should
1) Have some text on the authentication page to say that cookie's should be enabled
2) If authentication fails, suggest that cookies should be enabled.

Thanks.

[Martin Harvey]

I have just confirmed this using the emulator (running Honeycomb in this case). The first time through the browser, the login page has a URL including a /oAuth.action? which very quickly changes to a /Login.action? However, after logging in, the browser just stays in the login page. Switch cookies back on and the login redirects to /oAuth.action? and the Allow Access page.

For now, I am going to add a note to my authorisation page that cookie's must be enabled.

[Julien Boedec]

Yes, you are correct: cookies must be enabled in the OAuth flow.