E-PIA: Chrome/Edge Browser error "Blocked a frame with origin https://<domain.name> from accessing a cross-origin frame."
(Doc ID 2874480.1)
Last updated on FEBRUARY 01, 2024
Applies to:
PeopleSoft Enterprise PT PeopleTools - Version 8.54 and laterInformation in this document applies to any platform.
Goal
The issue is reported when end-users access Peoplesoft Applications through Chromium-based browsers. PeopleSoft Unified Navigation scenario such as accessing Remote CREF from the Portal system fails with the following error -
"An embedded page at <domain.name> says
Blocked a frame with origin https://<domain.name> from accessing a cross-origin frame."
Relaxing the same-origin policy by setting "document.domain" is deprecated, and is disabled by default in Chrome 115, released around July 2023. To continue using this feature, please opt out of origin-keyed agent clusters by sending an Origin-Agent-Cluster: ?0 header along with the HTTP response for the document and frames. See https://developer.chrome.com/blog/immutable-document-domain/ for more details.
PeopleSoft's usage of document.domain
document.domain is set to allow cross-frame communication which is commonly needed in Classic pages and sizing modals. This is required to access top.window and the target(iframe) content's contentWindow or contentDocument properties. Failure to set document.domain will cause a javascript error that will throw a permission denied error when trying to access another frame's property. This is very important when one frame is from site A and another frame is at site B. This setup is common in a cluster environment where the portal header is running Interaction Hub at site A and the target content is running at site B.
This behavior can also affect Fluid as well where the content within an iframe is located from another origin. This may include Activity Guide Wrappers (including Nav Collection), Interactive Grouplets/Tiles, and Modeless Context. Fluid is not immune to this problem. This affects all applications.
CAUSE:
The issue is caused due to a 3rd party browser change.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |