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

KB234798: Authentication is required when open a URL API link that has different letter case with the URL browsing MicroStrategy Web


Community Admin

• Strategy


When user open a URL API link from MicroStrategy Web, but the URL API has a different letter case that the URL customer is visiting current MicroStrategy Web page, re-authentication is required. If user is in application server such as Tomcat or WebSphere, user may get a 404 error for the requested page.

SYMPTOM:
When user open a URL API link from Strategy Web, but the URL API has a different letter case that the URL customer is visiting current Strategy Web page, re-authentication is required. If user is in application server such as Tomcat or WebSphere, user may get a 404 error for the requested page.
 
STEPS TO REPRODUCE:
1. In a Strategy Report Service document, create a simple URL API with non-capitalized letters, as shown below:


http://<Web Server Name>/Strategy/asp/main.aspx?evt=4001&src=Main.aspx.4001&Server=xxx&Project=xxx&reportID=xxx

 
2. In browser, open Strategy Web with default URL like below:

http://<Web Server Name>/Strategy/asp/Main.aspx

 
3. Open the URL API, note, user are projected for project credentials in IIS environment or get 404 error when using Tomcat or other jsp web server.
 
CAUSE:
This is working as expected, the path part of the URL should be consider as case-sensitive. Although in IIS, folder name in file system is not case-sensitive, which makes both links work, but for Strategy Web where session and cookie are involved, URL should be consider as case sensitive.
 
ACTION:
1. Make sure all end users are accessing same URL as the URL API;
2. Use following URL API instead of hardcoding web server and path in url:

./Main.aspx?evt=4001&src=Main.aspx.4001&Server=xxx&Project=xxx&reportID=xxx

 


Comment

0 comments

Details

Knowledge Article

Published:

June 12, 2017

Last Updated:

June 12, 2017