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

KB485448: Users are not able to login to MicroStrategy Library Admin page using Chrome browser. The Tomcat login screen does not show up, 401 Unauthorized error returns instead.


Elena Arman

Senior Support Engineer • Strategy


This article outlines issue with "HTTP Status 401 - Unauthorized" while logging in to MicroStrategy Library Admin page using Google Chrome browser.

Symptom

Users notice that when using Google Chrome browser to access the Strategy Library Admin page, Tomcat's login pop-up does not appear and the user receives the following error right away:

ka0PW0000007Q7RYAU_0EM4W000004Z4vn.jpeg

 “HTTP Status 401 - Unauthorized”

Cause

One possible cause is that the environment administrator has applied restrictions by setting Google Chrome policies that would block the usage of BASIC authentication.

Apache Tomcat's default authentication mode is Basic and Strategy uses this authentication mode as well set in the web.xml file located under the WEB-INF folder.

<login-config>        <auth-method>BASIC</auth-method>        <realm-name>Administrator Authentication Area</realm-name></login-config>

Chrome Policies can be changed in such a way that the “Supported authentication schemes” would disable Google Chrome browsers from allowing Basic authentication challenges altogether or only over non-secure HTTP connections. 
For example, and administrator can set 'HTTPS is required' in order to use the Basic authentication scheme. Then Google Chrome browsers would only allow Basic authentication challenges over HTTPS.
Note: If Basic is not specified under Supported authentication schemes, this setting is ignored.
 

Action

Reach out to your system admin to add BASIC authentication to the Supported authentication schemes or configure SSL for Tomcat Web Server. 
 

Workaround

If possible, use other browsers to access Strategy Library Admin page. Or configure the Strategy Library web.xml to use an allowed authentication method for Google Chrome that is also supported by Apache Tomcat, such as Digest authentication.


Comment

0 comments

Details

Knowledge Article

Published:

April 5, 2022

Last Updated:

September 25, 2025