Doesn’t seem to work 100% for me at least. Adding the force_verify parameter does show the authorization page, but when a user is already logged in and has to click the “not you?” link, the process gets stuck at http://api.twitch.tv/kraken/base.
- https://api.twitch.tv/kraken/oauth2/authorize?response_type=token&…
- user clicks “not you?”
- (browser goes to) https://api.twitch.tv/logout
- (browser goes to) https://api.twitch.tv/kraken/base
When sending the user back to the first url, he/she is still logged in.
Mind you, it works fine when I test it in Chrome for instance, but it doesn’t work when running it in Adobe AIR (desktop app).