Skip to main content

Support for different authentication environments

When you embed a dashboard in an application, you want it to display as easily and quickly as possible. This can mean seamlessly, without requiring that the user enter credentials at all, or simply scanning a QR code. The code you write to achieve this depends on how authentication is configured for the environment where the embedded dashboard is hosted. Examples or sample code are provided for different authentication environments.

  • Use guest authentication

    This introductory sample embeds an existing dashboard on the MicroStrategy demo server. Because only Guest authentication is enabled on the demo server, no credentials are required and the embedded dashboard is displayed seamlessly in the application.

    There are also instructions for customizing the sample to use a different server and dashboard. In order for the embedded dashboard to be displayed seamlessly in that environment, the server you use must be configured to have only Guest authentication.

  • Use guest authentication with multiple authentication modes enabled

    This sample illustrates how to seamlessly display an embedded dashboard in a simple application using Guest authentication, in an environment with multiple authentication modes enabled. The application includes code that specifically enables Guest authentication for the embedded dashboard.

  • Use standard authentication

  • Use SAML or OIDC authentication

    This sample illustrates how to embed a dashboard using SAML and OIDC authentication.

  • Seamless login using identity token

    This page shows you the workflow and implementation of a seamless login experience if your user has already authenticated.


If you plan to use Embedding SDK on a web page on a different domain from your MicroStrategy environment, please also meet the following requirements. More information in

  1. Enable Cross-Origin Resource Sharing (CORS)
  2. Allow SameSite cookies

If you plan to use Embedding SDK on the same domain as your MicroStrategy, the above changes are not required.