Legacy Knowledge Base
Published Jun. 30, 2025

How to resolve Iframe requesting authentication multiple times in a clustered environment

Written By

Isaac Wilson

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • After including an iframe link in a 3rd party application for our clustered Liferay environment (and already setting the appropriate X-Frame-Options), users are experiencing repeated authentication prompts even though they are already logged into Liferay
  • In the browser console, we can see errors relating to invalid X-Frame-Options header and restricted access due to cross-origin framing:
    Invalid 'X-Frame-Options' header encountered when loading 'https://webserver-url.com/': 'ALLOW-FROM http://localhost:8085/' is not a recognized directive. The header will be ignored. ...
    Uncaught DOMException: Failed to read a named property 'href' from 'Location': Blocked a frame with origin "https://webserver-url.com" from accessing a cross-origin frame. ...
    Failed to load resource: the server responded with a status of 403

Environment

  • Liferay DXP

Resolution

  • This issue is caused by a mismatch in SameSite values being applied between the application server's cookies and the web server's cookies, and can be resolved by ensuring the SameSite values are aligned for the configured domains and their associated cookies

Additional Information

 

 

 

Did this article resolve your issue ?

Legacy Knowledge Base