OpenFrame: Incoming message ignored due to origin mismatch

Louis Hawkins
Kilo Explorer

When trying to use the OpenFrame API window messages are blocked due to origin when loading HTML from hosting location. What is required to whitelist my origin?

2 REPLIES 2

Kiran Ramanna
ServiceNow Employee
ServiceNow Employee

add your host to `glide.ui.concourse.onmessage_enforce_same_origin_whitelist` property

Heraldo Valent1
Kilo Contributor

If you are getting the following error in the browser console:

Incoming message ignored due to origin mismatch.
OpenFrame init failed.. Openframe init request timed out
initFailure @ app.html:20
(anonymous) @ openFrameAPI.min.js:3
setTimeout (async) 
(anonymous) @ openFrameAPI.min.js:3
init @ openFrameAPI.min.js:3
init @ openFrameAPI.min.js:3
loadOpenFrame @ app.html:23
onclick @ app.html:28

This is because the origin of the Openframe needs to be "white-listed", and this is achieved by adding such origin in the following system property:

glide.ui.concourse.onmessage_enforce_same_origin_whitelist

For example, if the origin of the Openframe were to be https://localhost:8080/index.html, you should add https://localhost:8080.

Here are the instructions on how to setup system properties: https://docs.servicenow.com/bundle/london-platform-administration/page/administer/reference-pages/ta...

We were also struggling with this issue, and couldn't find any documentation related to it, maybe this answer helps someone else in the future. And it would be really good if such essential configuration is added to the Openframe configuration guide (or at least mentioned!): https://docs.servicenow.com/bundle/madrid-customer-service-management/page/product/customer-service-...