#stripeconnectplatform-oauth

1 messages · Page 1 of 1 (latest)

shut vessel
#

@night vault can you say a bit more?

#

there's no request id if there's no API key

night vault
#

It's weird. The 'code' and 'api_key' which is the 'platform_secret_key' are present.

#

response = HTTParty.post(uri, :body => { :client_secret => "#{platforms_secret_key}", :code => code, :grant_type => "authorization_code" }.to_json, :headers => { 'Content-Type' => 'application/json' } )

#

Did anything change on Stripe's side?

shut vessel
#

I'm sorry I'm struggling to follow. What's that call? What is happening? I'm missing a bit of context here

night vault
#

Oauth2 to connect a standard Stripe account to our platform. Currently just in development / test mode

#

I am confused since I have not updated this flow in a very long time.

shut vessel
#

I just tried on my end and it works fine so it's not widely broken. I do think it's more likely that the code has changed or the params are not passed as expected.
Can you properly log all those values?

#

(don't share them)

night vault
#

sk_test_xxxx

shut vessel
#

Do you know which account id you're working with? Trying to figure out how to debug this as all the values are secret values in that call

night vault
#

and connecting that to our platform:
acct_183tJHHnzkM7EAuH

shut vessel
#

hmmm that account is already connected too

#

Trying to figure out how to splunk for this, give me a few minutes

night vault
#

maybe i will deauthorize and try again?

shut vessel
#

yeah try that just to test and I'm looking at our logs

night vault
#

Nope

#

Deauthorized and tried to authorize again

shut vessel
#

okay we shouldn't do that but it's all test mode

#

can you DM me the ac_123?

#

I can try and track down your request from it

night vault
#

ok thank you. Just DM'd you.

shut vessel
#

waiting on the correct value

#

I need the ac_123 the authorization code that is in the URL, the think you exchange and pass in the code on your example request

#

(got it, looking)

#

Okay we never received that request. How easy is it for you to run the request by hand first with curl and then trying again with hardcoded values?

night vault
#

I will have to revisit this tomorrow. About to jump into a meeting....Thanks for trying.

shut vessel
#

Sure. I don't think anything is obviously broken so I'd recommend trying the raw HTTP request with curl first and hardcoded values

shut vessel
#

@night vault we have someone else reporting the same issue so I'm digging further into it as something might have changed. Will update you here based on what I find

shut vessel
#

Okay we rolled back a change on our end. The issue is that the code you shared uses JSON for the parameters. It's in theory not supported, and it should have never worked. So we completely missed that some integrations did that. I can reproduce your error if I send the parameters as JSON