isaacsanders/omniauth-stripe-connect

Issues

• Release new gem version for Omniauth v2 support

  #67 opened 2 years ago by olbrich
  7

• Support Omniauth v2

  #65 opened 2 years ago by espen
  0

• _method param being sent to Stripe Connect

  #57 opened 2 years ago by daveharris
  3

• Email is coming through as nil

  #63 opened 4 years ago by KarlBishop
  0

• Support suggested_capabilities param

  #61 opened 4 years ago by jongaegler
  0

• Support Stripe Express Connect

  #60 opened 5 years ago by todddickerson
  0

• How to use the `state` parameter

  #59 opened 5 years ago by amiralgazi
  0

• Authentication failure - invalid_client: No such API key: Bearer

  #52 opened 7 years ago by micha1805
  2

• cannot upgrade Faraday due to omniauth-stripe-connect dependancies

  #58 opened 5 years ago by RSR312-206
  1

• Bundler could not find compatible versions for gem "faraday"

  #54 opened 6 years ago by erinburns
  2

• provider_ignores_state: true possible

  #34 opened 9 years ago by romeo4934
  15

• upgrade from 2.9.0 to 2.10.0 leads to `invalid_redirect_uri` error

  #48 opened 6 years ago by srt32
  8

• undefined method `provider' for nil:NilClass

  #53 opened 6 years ago by ddonche
  1

• multiple stripe account

  #50 opened 7 years ago by seb-sykio
  5

• Callback Route Not Matching

  #32 opened 10 years ago by septerr
  5

• error/solved: This authorization code has already been used

  #27 opened 10 years ago by markaharper
  5

• User is nil after call back

  #42 opened 8 years ago by Hatcher19
  7

• Incompatible with other omniauth solutions since version 2.10.0

  #44 opened 8 years ago by jonhue
  2

• Support latest version of omniauth-oauth2

  #41 opened 8 years ago by jeffblake
  2

• Documentation is nearly useless unless you intend to use Devise

  #40 opened 9 years ago by rlugge
  3

• user session not storing after callback

  #39 opened 9 years ago by dedles
  4

• Redirect_url not working ... Please help

  #19 opened 9 years ago by iftikhar0005
  56

• Uploaded Stripe app to Heroku now i get error omniauth: (stripe_connect) Authentication failure! invalid_credentials: OAuth2::Error, invalid_client: No such API key: Bearer

  #37 opened 9 years ago by farhan-syed
  5

• omniauth.auth returns nil

  #38 opened 9 years ago by tarr11
  1

• Pass params through to callback

  #36 opened 9 years ago by joryhatton
  3

• -

  #35 opened 10 years ago by xdmx
  0

• support for deauthorization?

  #31 opened 10 years ago by SergeyBukhman
  1

• making a POST request for access token through the gem

  #29 opened 10 years ago by mankind
  0

• Stripe Connect Redirect URI to be specified when connecting

  #12 opened 10 years ago by codespore
  5

• ?force_login=true not being passed to Stripe

  #17 opened 10 years ago by mattgoldman
  6

• "Test OAuth Flow" from Stripe Management Panel doesn't work

  #23 opened 10 years ago by isparling
  2

• No route matches problem

  #20 opened 10 years ago by salayhin
  2

• Handling of user deauthroize

  #26 opened 10 years ago by flapjackfritz
  1

• refresh_token is no where to be found

  #21 opened 10 years ago by todddickerson
  6

• OAuth based requests must use card tokens from Stripe.js, but card details were directly provided.

  #24 opened 10 years ago by medinarodelsamson
  0

• Invalid Redirect Url...when using production client id

  #18 opened 11 years ago by iftikhar0005
  0

• redirect_uri - Stripe API changes.

  #13 opened 11 years ago by chrischattin
  1

• Error after putting in the credentials

  #10 opened 11 years ago by iftikhar0005
  3

• How to get data from the callback

  #8 opened 12 years ago by tibbon
  5

• Usage documentation no-go for /auth/stripe_connect

  #7 opened 12 years ago by tibbon
  4

• Invalid Credentials on Production

  #4 opened 12 years ago by aneziocampos
  3

• invalid_client: No authentication credentials were provided.

  #2 opened 12 years ago by xdmx
  7

• Received wrong number of arguments. (ArgumentError)

  #1 opened 13 years ago by xdmx
  4