Shapediver iFrame with ServiceNow iFrame Component

Grasshopper ShapeDiver
,
1

Getting a “Validation Failed” Message in the iFrame, Bright PINK :grinning_face_with_smiling_eyes: so I know it’s not a ServiceNow Message.
I have the domain in the Shapediver white list.

Whitelist domain: dev278350.service-now.com
A simple ball & square .GH file with a field. called [ballv2-2 | ShapeDiver (https://www.shapediver.com/app/m/ballv2-2)
Require strong Authorization: unchecked
Model Direct Allow: Checked

When running the URL provided for the iFRAME code is not authenticated which makes sense as the ballv2-2 is not publicly available and no white listed. See PINK error message “Embedding not allowed for [https://www.shapediver.com] (https://www.shapediver.com/)”

SN
SN1676×468 23 KB

2

Can you provide a link to where the model is embedded (ideally) and, if not, a report of the browser console and possible network errors reported by the browser developer tools?

3

Any way to extend the Trial?
The error no longer shows I suspect the trial is over so embed is no longer a thing.
Where to send logs?

4

Your trial is still running, so embedding should work. You can take a screenshot or copy and paste here any errors reported by the console or the network tab of your browser developer tools.

5

Hi Bari, just quickly jumping in here. I extended your trial until Monday next week. I hope this extra time helps you clarify any issues with Mathieu.

6

Thank you
Whats the best way to send console logs and user name password for Mathieu to be able to run ServiceNow to see

7

There is no Pink message anymore. (no changes on ServiceNOW side)

here is a screenshot of Console Messages.

no error message and console
no error message and console1819×897 365 KB

8

The Generic response from ServiceNOW is

HTTP Response Headers

The document discusses HTTP response headers, specifically the Content-Security-Policy: frame-ancestors header, which can affect how a page is rendered in an iframe. If the iframe is not functioning, it could be due to incorrect configuration of this header. For example, if the header is set to ‘self’ and the iframe is trying to load content from a different domain, it will not be allowed. Additionally, Internet Explorer has specific handling for this header, and if the configuration is not set up correctly, it may not work as expected. However, the document does not provide specific information about a problem with a non-functioning iframe, so further investigation would be needed to determine the exact cause.

9

Please send a PM explaining how this can be reproduced (login credentials etc). The console message from origin 'null' suggests some unusual setup, which we can’t reproduce ourselves.

10

Many thanks for your PM. The platform you are using to embed the iframe seems to set the attributes allow and sandbox on the iframe element, which likely cause the problem. Please try to deactivate this, and use exactly the iframe code we provide. Another option might be to add the referrerpolicy attribute and set it to origin.

In general, please use the iframe code as supplied on our platform. The allow and sandbox attributes seem to prevent our viewer to detect the domain of the embedding page, and hence the check whether embedding is allowed fails.

In case you can’t find a solution, please book an onboarding call.