KB441419: The Embedding API fails to load when Internet Explorer 11 is used cross-domain

• Strategy

Communication between the website using the Embedding API and MicroStrategy Library, where the REST API is hosted, is subject to CORS if they're not on the same domain & port. Following KB000039583, IE11 remains unable to load any embedded dossiers.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
Communication between the website using the Embedding API and Strategy Library, where the REST API is hosted, is subject to CORS if they're not on the same domain & port. Following KB000039583, Strategy Library can be configured to whitelist specific origins in compliance with CORS.

Symptoms

In Strategy 10.10 & 10.11, if Strategy Library is running on a different port number, the Embedding API may silently stop loading part-way.
Only IE11 is affected. This issue cannot be seen with Google Chrome nor Firefox.
If custom authentication is enabled, one observation may be that the custom authentication callback (getLoginToken()) in the embedding API is never executed.

This can be tested by adding a breakpoint or "debugger;" statement into the callback, and refreshing the page with developer tools open.

The javascript console in F12 developer tools shows no errors or warnings.
One/both servers are running on the default HTTP/HTTPS ports (80/443)..

Cause

This is a known issue with the EmbeddingLib.js bundled with Strategy Library.

Action

Contact Strategy Technical Support for an update on this issue, with reference DE104701.

Workaround

The following workarounds have been found to this limitation, should a fix not yet be available:

Avoid using the default HTTP ports (80 for HTTP or 443 for HTTPS).
Or, host Strategy Library & the web application communicating with Library, on the same origin (same domain & port). This avoids the IE11 CORS limitation.

Comment

0 comments

Details

Knowledge Article

Published:

July 26, 2018

Last Updated:

March 21, 2024

Symptoms

In Strategy 10.10 & 10.11, if Strategy Library is running on a different port number, the Embedding API may silently stop loading part-way.

Only IE11 is affected. This issue cannot be seen with Google Chrome nor Firefox.

If custom authentication is enabled, one observation may be that the custom authentication callback (getLoginToken()) in the embedding API is never executed.

This can be tested by adding a breakpoint or "debugger;" statement into the callback, and refreshing the page with developer tools open.

The javascript console in F12 developer tools shows no errors or warnings.

One/both servers are running on the default HTTP/HTTPS ports (80/443)..

Workaround

The following workarounds have been found to this limitation, should a fix not yet be available:

Avoid using the default HTTP ports (80 for HTTP or 443 for HTTPS).

Or, host Strategy Library & the web application communicating with Library, on the same origin (same domain & port). This avoids the IE11 CORS limitation.