EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB324297: When executing a document containing an ESRI map, the web browser throws the warning message “This page is trying to load scripts from unauthorized sources” in MicroStrategy Web 9.x and 10.x


Community Admin

• Strategy


SYMPTOM:
In some instances, the below warning message is thrown by the web browser when executing documents containing ESRI maps. This has been seen when the web server is configured to use https. The image below is from Chrome; however, similar messages can be seen in other web browsers as well including Internet Explorer
 


This page is trying to load scripts from unauthorized sources. 

 

ka04W000000OajlQAC_0EM4400000025NB.jpeg

 
As stated in this article, this message is a browser warning and thus not a Strategy error.
 
STEPS TO REPRODUCE:

  1. Configure the web server to use https.
  2. Create a document containing an ESRI map.
  3. While using https, execute the document.
  4. Notice the web browser throws the message.

 
CAUSE:
The warning message appears because the web browser does not trust the ESRI address. One potential cause of this message appearing is the ESRI URLs use http while the web server uses https.
 
ACTION:
To avoid seeing the warning message, the esriConfig.xml file can be modified for the map server and map layer URLs to use https rather than http. Note that these URLs are in the esriCongif.xml file located at MSTR_Web_Installation\WEB-INF\xml\config. The esriConfig.xml file in the plugins folder does not contain the URLs for the map server and map layers.
 
After making these changes, restart the web server and clear browser caches for the changes to take effect.
KB324297


Comment

0 comments

Details

Knowledge Article

Published:

June 13, 2017

Last Updated:

November 28, 2018