Closed mattgoldman closed 9 years ago
@isaacsanders Any ideas on this?
I poked around but am pretty unfamiliar with Omniauth's inner workings. I was able to enable it manually in a fork. But it's not worthy of a merge. The Twitter strategy may be helpful: https://github.com/arunagw/omniauth-twitter/blob/master/lib/omniauth/strategies/twitter.rb#L39-L61
Nevermind, my solution didn't work. I'd be happy either passing force_login=true in the initializer, or in the OAuth link.
The docs make it sounds like this is currently possible. Can you let me know if I'm possibly doing something wrong/the right way to pass along params to Stripe?
I will look into this later this week. Just finished the quarter at school.
Hey Isaac, I just made a raw attempt and Stripe doesn’t seem to be listening to the force_login param.
I sent in a support request and will update this issue when I hear back in the coming days.
Don’t let this stress ya out ;-)
I wouldn’t be surprised if your strategy was working fine, and Stripe just wasn’t handling it as expected on their end.
On Nov 24, 2013, at 6:41 PM, Isaac Sanders notifications@github.com wrote:
I will look into this later this week. Just finished the quarter at school.
— Reply to this email directly or view it on GitHub.
Any updates on this?
Hi, it appears that when I pass
force_login=true
in the query string, it isn't being passed along to Stripe.I've checked with their support team and they've confirmed that they do support this param.
Do you know what could be causing this?
After connecting a certain Stripe account, if I click Connect to Stripe again: the oauth window opens, and subsequently closes, not giving me an option to login to another account.