Closed sdkilbo closed 2 years ago
I was able to resolve it with very specific gems. Dont know which one was the solution, all of these depended on each other.
gem "hashie", "3.6.0"
gem 'omniauth', "1.9"
gem "omniauth-rails_csrf_protection", "0.1.2"
gem 'omniauth-oauth2', "1.6"
gem "oauth2", "1.1"
gem "faraday", "0.8"
gem "jwt", "1.5.1"
I've also run into this issue and it appears to be an issue with either the omniauth-oauth2
or oauth2
gems. When fixing omniauth-oauth2
to 1.7.2, it works as expected.
run into the same issue, that's helped me @deanpcmad thanks a lot
After looking into it some more, I believe it's to do with the upgrade to oauth2
v2
https://github.com/oauth-xx/oauth2/blob/master/CHANGELOG.md#200---2022-06-21
Have found the issue and have created a PR.
In the mean time, you can use my fixed branch.
gem 'omniauth-twitch', github: "deanpcmad/omniauth-twitch", branch: "fix-auth"
Makes get response fine but will return back with 400 missing client_id on the post. Tried this with an empty project to no avail. I also tried with devise, figured that was the issue so I ran with just middleware with same issue.
Steps to reproduce:
rails new twitchomniauth -d mysql