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

KB484203: In the MicroStrategy for Office add-in, MicroStrategy Library with custom authentication results in an add-in error


Julia Sroka

Consultant • Strategy


This article addresses the add-in error experienced when using MicroStrategy Library with custom authentication in the MicroStrategy for Office add-in. This article also provides a solution to avoid this error.

Description


In the Strategy for Office add-in, Library with custom authentication does not work in browsers, such as Chrome, Mozilla Firefox, Internet Explorer, and Edge, in both Windows and Mac. The add-in does not load and returns the following error:
Add-in Error: Something when wrong and we couldn't start this add-in. Please try again later or contact your system administrator. 
 

ka02R000000bs9GQAQ_0EM2R0000019drp.jpeg

However, the desktop version successfully starts the add-in for Windows and Mac. 

Why is this happening?


Prior to loading any manifest file, Excel for the web first validates that the entry points is a valid add-in. To do this, it checks that the ExcelAPI initialization was done by the app. However, in a custom authentication environment, the ExcelAPI initialization path is incorrectly behind a security filter. Rather than loading the Strategy for Office authentication, Excel for the web redirects to the custom authentication form. This website doesn't have the ExcelAPI, and therefore is blocked by Excel.
This behavior is not present in the desktop application because the validation does not occur.

Solution


To use custom authentication,

/static/mstr-office-loader
and
/api/session/
must be ignored or unprotected. 


Comment

0 comments

Details

Knowledge Article

Published:

April 21, 2020

Last Updated:

April 21, 2020