The browser refuses to show Keycloak inside a frame from my React app
violating Content Security Policy directive: frame-ancestors 'self'Short answer
Keycloak sends headers that stop other sites from framing its pages, to prevent clickjacking. When your React app's origin loads Keycloak in an iframe, the browser enforces frame-ancestors 'self' and refuses. Add your app's origin to the Content-Security-Policy field in Realm Settings, Security Defenses, and keep the X-Frame-Options field consistent.
Fix it fast
1Find out which cause you have
Open the browser developer tools, load the page that shows the error and read the content-security-policy response header of the framed Keycloak URL.
# Developer tools > Network > select the Keycloak request > Response headers > content-security-policy2Match what you see, then jump to its fix
What does the error look like?
violating Content Security Policy directive: frame-ancestors 'self'
Cause 1 of 2
Your app's origin is not allowed by the realm's Content-Security-Policy
1Check
Keycloak's administration guide says its default headers block framing of its login pages, so that other websites cannot include a login dialog in an iframe. CSP's frame-ancestors decides which parents may embed a page.
# Admin Console > Realm settings > Security defenses > Content-Security-Policy2Fix
In Realm settings, Security defenses, add your app's origin to the Content-Security-Policy field, with the exact scheme, host and port.
frame-ancestors 'self' https://app.example.com3Verify
Save, reload the app and check that the iframe now loads and the response header lists your origin.
# Developer tools > Network > content-security-policy headerConfirmed by keycloak.org
Cause 2 of 2
The X-Frame-Options field still blocks the frame
1Check
Keycloak's guide tells you to enter the allowed origin in both the X-Frame-Options and Content-Security-Policy fields. The CSP specification says X-Frame-Options is ignored when an enforced policy applies, so modern browsers follow the CSP.
# Admin Console > Realm settings > Security defenses > X-Frame-Options2Fix
Update the X-Frame-Options field to match what you allow in the CSP, as the guide describes, and keep the two in step.
# no command: edit both fields in Security defenses and save3Verify
Reload the page and read both headers in the response.
# Developer tools > Network > Response headersConfirmed by w3c.github.io
How do I stop it coming back?
- Allow only the exact origins that must embed Keycloak; do not remove frame-ancestors altogether.
- Change the headers per realm, and test the admin console after each edit.
- Prefer a normal redirect login over an iframe when you can.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fixWeb apps
Axios request is not cancelled when a React component unmounts
A cancelled request is logged as an error in the catch block
Axios cancels a request when you pass it an AbortSignal and later call abort() on its controller.
4 causes, each with a fix