-
Notifications
You must be signed in to change notification settings - Fork 75
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
upgrade from 2.9.0 to 2.10.0 leads to invalid_redirect_uri
error
#48
Comments
We did some research and found that overriding the Related issue: omniauth/omniauth-oauth2#93 (comment) 🌞 |
@srt32 @ryanclark2 @chrt00 PR #47 has the relevant method, but it is buried under adding the use of a JWT to the gem. I would be happy to merge a PR with just the |
@isaacsanders Yup, that's exactly what we did. If you'd like a PR with just that in it, let me know. |
I'm into it. |
As in, yes, I would like a PR, and will merge it in/cut a release. |
Ha, I caught your drift. I'll send it over it a short bit. Thanks. |
…Stripe doesn't support them - Addresses: isaacsanders#48
Version 2.10.1 released |
@srt32 @ryanclark2 If either of you two are still working on this, I would appreciate it if you would confirm that 2.10.1 fixes the issue for you. |
We recently upgraded from 2.9.0 to 2.10.0. Upon upgrading we experienced the below
invalid_redirect_uri
error that we did not see before the upgrade.This version bump seems to only bump transitive dependencies. Is there any updated config needed to make the new version work properly?
Thanks!
The text was updated successfully, but these errors were encountered: