Using External links as documents, what are the requirements to appear on the wizard?

Hello,

I am re-opening again this topic to check if there a feasible solution for this, or it is not possible. Our customer leitmotiv is trying to access his internal website however it is blocked.

Description

I setup a document with an external link (website). On track in I wish to see on the document the website I added.

However, is it possible to share an understanding why in some cases the website appears whilst in other seems to be the website refusing the connection? Is it a missing security token, or is it by design like so, or some site can be accessed…

Example:

In the documentation we have this warning. But cannot make much understanding of the delta:

image

Any clues I appreciate. Thanks. Regards.

Hi all,

I remember this discussion via teams and one of the answers that seem to be the solution was this one:

"
The reason can be a bit more technical. It is possible that the system will not render the external page, because the website was not configured as an “Allowed Origin” in the CORS Security setting when installing the environment through DevOps Center ( Installation - Critical Manufacturing Documentation Portal )

"

At the time we tried this in our integration environments but without sucess, could this be because of our internal network policies?

Best Regards,
JoĂŁo Querido

Hi!

This also depends on whether the external site allows its content to be framed. Some sites allow their pages/files to be displayed inside an iframe, while others explicitly block it, and in that case the browser shows the “refused to connect” message instead of the document.

You can check whether a given site allows it with these steps:

  1. Press F12 to open the Developer Tools.
  2. Display the Document in MES (as you did)
  3. If the site blocks embedding, you’ll see a message in the console such as:
    Framing '<url>' violates the following Content Security Policy directive: "frame-ancestors 'self'". The request has been blocked.
    or Refused to display '<url>' in a frame because it set 'X-Frame-Options' to 'sameorigin'.

In the case I tested, the site returns frame-ancestors 'self', which means it only allows itself to embed its own pages. This is a restriction set by the external site, so there’s nothing we can change in the MES to work around it.

If the document is being hosted by the customer, they can also change the properties to allow being framed.

Best Regards,

Mário Gomes