Iframes and Running Apps

Introduction

By default, a Mendix app is blocked from running inside an iframe. This is to protect the end-user from attacks using clickjacking. There is more information on this in the Adding HTTP Headers section of How To Implement Best Practices for App Security.

You can enable your app to run inside an iframe by setting the frame-ancestors directive of the Content-Security-Policy HTTP header for your node’s environment. For Mendix Cloud, this can be done within the Mendix Portal, as described in the HTTP Headers section of Environment Details.

There is more information about iframes on Mendix Cloud in the Running Your App in an Iframe section of Environment Details.

You can also set the obsolete X-Frame-Options HTTP header if you need backward compatibility.

Resolving Browser Issues

Most browsers have additional security to ensure that iframes are only allowed when they are from the same domain as the main page. If your app does not have the same domain as the main page containing the iframe, it will only run if the SameSite cookie is set to allow this. You can find a good explanation of SameSite cookies in SameSite cookies explained on the web.dev website.

When running your app in Mendix Cloud, you can set the SameSite cookie through a custom runtime setting as explained in the Running Your App in an Iframe section of Environment Details.

If your app is deployed outside Mendix Cloud (on premises, for example), then you will need to configure your webserver to set the SameSite cookie to the correct value.