Getting this error message when trying to embed Engagement Messenger onto my clients site
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 07:42 AM
Getting this error message in my console:
AMB getClient() tried to access parent from an iFrame. Caught error: SecurityError: Failed to read a named property 'g_ambClient' from 'Window': Blocked a frame with origin "https://devxxxxx.service-now.com" from accessing a cross-origin frame.
I have created a CORS rule and HTTP response header and the frame looks like that in the attached picture. I have also set my glide.set_x_frame_options system property to false.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
Did anyone find the solution already?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
The most common cause of this error for our customers is due to third-party integrations on their site creating and interacting with iframes.
Third-party integration scripts–such as help-chat, cookie management, and review widgets–often need to create and interact with a custom iframe on the customer site.
The origin of the integration script is considered the customer site as this is where the script lives. However, if the iframe this script creates has a src attribute set to a different origin, then the script will be unable to access the iframe. Any attempt by the script to access the iframe’s contents will trigger the frame blocked error.
Source: Blocked a frame with origin "xyz" from accessing a cross-origin frame | Noibu Knowledge Base
