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

KB484692: "Error in login Please contact your Administrator" is returned intermittently in Chrome when accessing MicroStrategy Web with SAML enabled


Yanqing Liu

Cloud Support Expert I • MicroStrategy


This article explains why a login error is returned in Chrome when accessing MicroStrategy Web with SAML enabled. This article also provides a solution to avoid this behavior.

Description 


The following error is experienced intermittently in Chrome when accessing Strategy Web with SAML enabled.
Error in login
Please contact your Administrator. 
 

ka04W000000XO35QAG_0EM4W000001JZOk.jpeg

You can further troubleshoot this issue: 
 

  • SAML Log: To get more detailed information, you can edit
    log4j.properties
    under
    <Strategy Web Application>/WEB-INF/classes
    and set all the log levels to DEBUG. Restart the web application server after making the change. Please remember to change the log level back to ERROR after troubleshooting. 
    With the scenario reproduced, you can see the following exceptions in the SAML log:
    09/15/2020 09:08:24,070 org.springframework.security.saml.storage.HttpSessionStorage DEBUG - Message a2cac57i68ha2ij92190ebhf3cd3c40 not found in session 5D65B46C47B5C3356701BDB7D45E229F 09/15/2020 09:08:24,070 org.springframework.security.saml.SAMLAuthenticationProvider DEBUG - Error validating SAML message org.opensaml.common.SAMLException: InResponseToField of the Response doesn't correspond to sent message a2cac57i68ha2ij92190ebhf3cd3c40

  • Fiddler log: From the fiddler log, you can that
    JSESSIONID
    was lost and a new
    JSESSIONID 5D65B46C47B5C3356701BDB7D45E229F
    was created when sending the request, 
    POST /MicroStrategy/saml/SSO
    .
ka04W000000XO35QAG_0EM4W000001JZOz.jpeg
  • Additionally, from the above screenshot taken from the fiddler log, the SameSite cookie attribute is not set for
    JESESSIONID.

Why is this happening?


Since Chrome 80, if the SameSite cookie attribute is not configured, it will be set to “Lax” by default. SAML configured with SP initiated POST Binding is affected if the Strategy application servers are in a different domain from the SAML authentication Identity Provider domain.

Solution


Refer to the steps in Chrome v80 Cookie Behavior and the Impact on MicroStrategy Deployments.


Comment

0 comments

Details

Knowledge Article

Published:

November 9, 2020

Last Updated:

November 9, 2020