-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always redirects to /auth/failure with message invalid_credentials #8
Comments
can you show how are you initializing the gem? make sure to obscure used credentials. |
omniauth.rb
Gemfile (Gems I'm using just in case):
|
Hello guys. First off, happy new year to you guys! Any leads to this? Any help would be appreciated. |
I also have the same problem when i use facebook as login. I'd be happy to have a solution for this. thanks advance. |
+1, this is with 0.0.9. Any leads on this? The gem just flat out doesn't work for me at the moment. |
can you try some of the potental workarounds listed here? #7 (comment) |
@masterkain it appears omniauth-oauth2 has permanently added the query string back to the callback_url in v1.4.0 and doesn't seem to be planning to remove it. other projects such as omniauth-google-oauth2 have permeantly locked on omniauth-oauth2 1.3.1 until it's fixed, or overriding the callback_url in the strategy. we resolved by manually setting a gem dependency for an early version of omniauth-oauth2. perhaps it's worth locking omniauth-spotify below 1.3.1 or overriding callback_url in the strategy? |
icoretech/omniauth-spotify#8 (comment) zquestz/omniauth-google-oauth2#205 Google OAuth 2 talks about the problem with new Omniauth version's callback_url. Manually specific the callback url to remove the query string
Hello guys. I need to use
omniauth-spotify
but there seems to be an error I always get. It always redirects me to/auth/failure
directly even before I get to do anyputs
on my callback action.I have on my Spotify App is
callback: http://localhost:3000/auth/spotify/callback
I can provide more info if I need to.
The text was updated successfully, but these errors were encountered: