#heildever
1 messages · Page 1 of 1 (latest)
Can you share the stripe-app.json content?
Sure, the whole file?
Particularly the part that's erroring
"connect-src": [
"'self'",
"https://api.partnerstack.com/api/integration-connections"
],
"image-src": null,
"purpose": "Enables PartnerStack Stripe App to communicate with the PartnerStack API."
}
},```
You see anything wrong?
Asking a colleague
Will get back to you
They said you need to remove 'self'. With apps you don't need that (unlike a website a stripe app is slightly different.
I had 'self' on a previous version and the app was able to make requests, the HTTP requests are blocked since I removed 'self'
hey there, just popping in to help, i was looking into this
The spec indicates those should be URLs: https://stripe.com/docs/stripe-apps/reference/app-manifest#csprequest
Where is that request going? Is it blocked by CSP specifically?
We had to remove 'self' because we werent able to upload our new version
Now these requests, going to our own backend, are being blocked. There are no changes the config and the backend. I can also confirm that the requests work fine locally as soon as I put self back
Leads me to think removing self causes requests to be blocked by CSP 🤔
What's the complete URL of that request being blocked?
Can you try adding it using the cli as shown here: https://stripe.com/docs/stripe-apps/build-ui#use-third-party-apis
Url is defined under 'self' in content-src, json I posted above
Can you show that on the blocked request for posterity?
Just want to make sure there isn't a mismatch
Can you try removing the content_security_policy and re-adding via CLI?
With or without 'self'?
And does it work when running locally using stripe apps start to test?
yup
without, just using stripe apps grant url "https://api.partnerstack.com/api/integration-connections" "Send data to backend service..."
And this block happens while testing with it running locally?
I think the best course right now is to write in to our support team with the two specific versions and this self CSP difference along with this example request blocking.
https://support.stripe.com/contact
This seems like its unexpected, or that the CSP you configure is not being applied as expected.
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
This is producing a CSP error in the console, too?
GET https://api.partnerstack.com/api/integration-connections net::ERR_BLOCKED_BY_CLIENT
I dont understand how I was able to upload a version with 'self' in the manifest, now the same config doesnt work
If its blocked by CSP, there should be an explicit console message saying so
I'm not sure either! I would say you should include both versions of that aprt of your config, and indicated what happens in each case
(previous version with self works, new version can't be uploaded with self, request seems to be blocked without it etc)
Sounds good