-
Notifications
You must be signed in to change notification settings - Fork 212
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
Add CSP to the payments-server #1923
Comments
I found some docs on the CSP config required for the Stripe JS to work: https://stripe.com/docs/security#content-security-policy |
Remove payments/content consolidated CSP, fix Prettier-ified files, create separate middleware for payments Fix prettier things Add Stripe CSP things to payments server Add more config vars into proper directives Add stripe checkout API Remove unneeded directive Add tests to csp.test.js Remove unneeded test no-CSP lines Remove isCspRequired check in payment server (not content server) csp.enabled true by default Update CSP violations to report to content server Template literal return for getOrigin
Remove payments/content consolidated CSP, fix Prettier-ified files, create separate middleware for payments Fix prettier things Add Stripe CSP things to payments server Add more config vars into proper directives Add stripe checkout API Remove unneeded directive Add tests to csp.test.js Remove unneeded test no-CSP lines Remove isCspRequired check in payment server (not content server) csp.enabled true by default Update CSP violations to report to content server Template literal return for getOrigin Update Stripe url doc
Remove payments/content consolidated CSP, fix Prettier-ified files, create separate middleware for payments Fix prettier things Add Stripe CSP things to payments server Add more config vars into proper directives Add stripe checkout API Remove unneeded directive Add tests to csp.test.js Remove unneeded test no-CSP lines Remove isCspRequired check in payment server (not content server) csp.enabled true by default Update CSP violations to report to content server Template literal return for getOrigin Update Stripe url doc Address PR things
Remove payments/content consolidated CSP, fix Prettier-ified files, create separate middleware for payments Fix prettier things Add Stripe CSP things to payments server Add more config vars into proper directives Add stripe checkout API Remove unneeded directive Add tests to csp.test.js Remove unneeded test no-CSP lines Remove isCspRequired check in payment server (not content server) csp.enabled true by default Update CSP violations to report to content server Template literal return for getOrigin Update Stripe url doc Address PR things Add DATA back to payments CSP
Remove payments/content consolidated CSP, fix Prettier-ified files, create separate middleware for payments Fix prettier things Add Stripe CSP things to payments server Add more config vars into proper directives Add stripe checkout API Remove unneeded directive Add tests to csp.test.js Remove unneeded test no-CSP lines Remove isCspRequired check in payment server (not content server) csp.enabled true by default Update CSP violations to report to content server Template literal return for getOrigin Update Stripe url doc Address PR things Add DATA back to payments CSP Change variable name and only add in development
chore(fxa-payments-server): fixes #1923 - add CSP to the payments server
The CSP is not super useful at the moment because it allows unsafe styles. Could we get that removed? |
If I recall, we need |
Seems a little involved, spinning off as a separate sub-issue from #1128.
We might be able to reuse the CSP-related middleware from the fxa-content-server package.
The text was updated successfully, but these errors were encountered: