Replies: 1 comment 2 replies
-
|
We have this in our yaml dex config: Works great, we see the header added to the login page html returned. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
Hello all,
Context
In my company we are using Dex. We realized that the Dex web application is vulnerable to clickjacking attack (see more about clickjacking here).
An effective way to protect against Clickjacking (it is the recommandation to be exact), is to send
Content Security Policy(CSP) frame-ancestors directive response headers.Issue
We did not find a way to use this header with the Dex web app response.
We see that equivalent configs are in place for the CORS policy (with the AllowedOrigins field in the web config) and we were hoping something similar for CSP header as these two cases are similar as they allow us to set the security context of the web app.
This brings us to the question, how could we prevent Clickjacking on dex web app?
Beta Was this translation helpful? Give feedback.
All reactions