MicroStrategy ONE
Linking to a MicroStrategy Report from an External Web Site or Other Location
You can access any MicroStrategy report from an external Web site or other location by providing the correct URL parameters, including authentication and authorization information. For MicroStrategy Web pages that require login, you can have the user be prompted for credentials or you can pass the credentials in the URL. The following scenarios are described below:
There are many situations in which it is not advisable to pass credentials in the URL.
Prompting the user for login credentials
The following URL requests that the Electronics Revenue vs. Forecast report in MicroStrategy Tutorial (located under Public Objects/Reports/Subject Areas/Sales and Profitability Analysis) be displayed. Because this request requires a login, the user is prompted to enter credentials before the report is displayed. In a prompted report, the Prompt Question page is displayed after successful login so the user can select the prompt answers to be used for the report.
J2EE environment:
<a href="http://webserver/MicroStrategy/servlet/mstrWeb?server=INTELLIGENCE_SERVER&project=MicroStrategy+Tutorial&evt=4001&reportID=EB3CD5D14F4C8C77782AC0882C986B8D">Electronics Revenue vs. Forecast</a>
.NET environment:
<a href="http://webserver/MicroStrategy/asp/Main.aspx?server=INTELLIGENCE_SERVER&project=MicroStrategy+Tutorial&evt=4001&Main.aspx.4001&reportViewMode=1&reportID=EB3CD5D14F4C8C77782AC0882C986B8D">Electronics Revenue vs. Forecast</a>
The parameters passed in the URL are described below:
Parameter | |
---|---|
server
|
Name or IP Address of MicroStrategy Intelligence Server
|
project
|
Name of project to be accessed
|
evt
|
Event associated with the user action. A list of event IDs can be found in events.xml, as well as the Event Handlers Reference.
|
reportID
|
Identifier for the report to be accessed While it is possible to reference a report by its name in the URL, this is not the recommended practice because of potential problems. For example, the report name changes with the user's locale, and the URL breaks if the report name is not properly encoded.
|
Passing the login credentials in the URL
The following URL automatically displays the Electronics Revenue vs. Forecast report in MicroStrategy Tutorial (located under Public Objects/Reports/Subject Areas/Sales and Profitability Analysis). The user is not prompted for login information before displaying the report since the login credentials (shown in bold below) are supplied in the URL. In a prompted report, the Prompt Question page is displayed automatically so the user can select the prompt answers to be used for the report.
J2EE environment:
<a href="http://webserver/MicroStrategy/servlet/mstrWeb?server=INTELLIGENCE_SERVER&project=MicroStrategy+Tutorial&evt=4001&reportID=EB3CD5D14F4C8C77782AC0882C986B8D&uid=username&pwd=password">Electronics Revenue vs. Forecast</a>
.NET environment:
<a href="http://webserver/MicroStrategy/asp/Main.aspx?server=INTELLIGENCE_SERVER&project=MicroStrategy+Tutorial&evt=4001&Main.aspx.4001&reportViewMode=1&reportID=EB3CD5D14F4C8C77782AC0882C986B8D&uid=username&pwd=password">Electronics Revenue vs. Forecast</a>
The parameters passed in the URL are described below:
Parameter | |
---|---|
server
|
Name or IP Address of MicroStrategy Intelligence Server
|
project
|
Name of project to be accessed
|
evt
|
Event associated with the user action. A list of event IDs can be found in events.xml, as well as the Event Handlers Reference.
|
reportID
|
Identifier for the report to be accessed While it is possible to reference a report by its name in the URL, this is not the recommended practice because of potential problems. For example, the report name changes with the user's locale, and the URL breaks if the report name is not properly encoded.
|
uid
|
User name or login name for the user |
pwd
|
Password for login
|
See also
-
Web Authentication: Authentication integration and Single Sign-on
-
Web Authentication: External Security Mechanism
-
Advanced Customization Topics: Integrating External Security
-
Scenarios: Extending Existing or Adding New Functionality: Answering a Prompt Question by Supplying Custom Parameters in the URL