Hot answers tagged

2

I don't think that's a bug, for implicit OAuth. Anyway, if I understand RFC 6749 correctly, that is not how you are supposed to do such extra checks. Use the state parameter. And this works. For example, a call to:   /oauth/dialog?...&state=robfoo&redirect_uri=https://stackexchange.com/oauth/login_success (Click the link and try it.) Yields ...


2

This is what the /apps/{accessTokens}/de-authenticate route does. Passing valid access_tokens to this method causes the application that created them to be de-authorized by the user associated with each access_token. This will remove the application from their apps tab, and cause all other existing access_tokens to be destroyed. (Emphasis added) So if ...


1

Refer to the API Authentication docs; there are a great many things wrong with the URL in the question (at least 5). For starters, it's to the wrong path. stackoverflow.com/oauth/authorize gives helpful messages/results like: Oops! Something Bad Happened! Authorization attempt not valid for current user Authorization attempt unauthorized Couldn'...


1

I get the reason: Do not use gem 'omniauth-stackexchange', '~> 0.2.1' ,but instead of gem 'omniauth-stackexchange', git: 'https://github.com/nashby/omniauth-stackexchange.git' The reason see this:add call back url


1

I don't know about that Ruby/Gem, but your app registration is not correct. You need to configure your app for explicit OAuth2, per this other answer, except enter localhost instead of example.com. (The localhost is based on the original version of the question. If you have a registered domain, use that.) Then, in your ruby code: config.omniauth: ...


1

I had the same problem. According to the authentication docs‡: In order to get access_token and expires (if applicable) wrapped in a JSON object, POST to https://stackoverflow.com/oauth/access_token/json instead. ‡ Now. The Doc pages did not say this back in 2013.


Only top voted, non community-wiki answers of a minimum length are eligible