Skip to content
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

Update stripe connect and omniauth gems #1012

Merged
merged 4 commits into from
Jan 29, 2025

Conversation

jagthedrummer
Copy link
Contributor

This switches out a dependency for Stripe Connect.

We used to use omniauth-stripe-connect but it hasn't been updated in quite sometime and it's pegged to versions of ominauth on the 1.x line. Unfortunately the 1.x line of ominauth has some security vulnerabilities. In order to update omniauth to the 2.x line we're moving to omniauth-stripe-connect-v2 which is basically the same as omniauth-stripe-connect but with a .gemspec that allows omniauth versions ~> 2.0.

This also bumps the version of omniauth-rails_csrf_protection to ~> 1.0 so that it works with the new stripe connect gem.

The docs for all of the new versions are the same as the docs for the old versions, so there shouldn't be any application changes required. I've tested these in my local starter repo and I can connect to Stripe accounts both for user sign in and for purposes of creating a Stripe Installation for marketplace scenarios.

Fixes #1007

@jagthedrummer jagthedrummer merged commit 6c6e534 into main Jan 29, 2025
36 checks passed
@jagthedrummer jagthedrummer deleted the jeremy/stripe-connect-update branch January 29, 2025 19:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update bullet_train-integrations-stripe's outdated omniauth dependency
1 participant