Strategy One

Export and Import Database Logins and Vaults

Starting in Strategy One (May 2026), you can bulk export and import database logins and vaults from your Intelligence Server and import them into the Strategy Gateway Agent. This method allows you to migrate database connection credentials between environments without having to manually recreate connections.

Use the export and import functionality to utilize the following:

  • Export one or more database logins with their associated vault dependencies.

  • Export credentials in encrypted or plaintext format.

  • Import logins and vaults directly into the Strategy Gateway Agent.

  • Preserve vault configurations including TLS certificates and authentication credentials.

Certified vault types include AWS Secret Manager, Azure Key Vault, CyberArk, and Google Secret Manager.

Prerequisites

Intelligence Server Requirements

  • Strategy One (May 2026) or later with database login export API support

  • You must have the Use Database Login Manager and Create and Edit Vault privileges.

    The Create and Edit Vault privilege is only required if a database login is vault-based.

  • You must have Read access to the database logins and vault dependencies.

Strategy Gateway Agent Requirements

You must be on the same version as the Intelligence Server.

Export Database Logins from the Intelligence Server

  1. Determine which database logins you want to export. You can export the following:

    • Specific database logins by their GUIDs

      To find database login GUIDs, use the Strategy REST API or Workstation interface.

    • All database logins in the environment

  2. Open the Strategy REST API Explorer by appending your environment URL that ends with /MicroStrategyLibrary with /api-docs/index.html?visibility=all in your browser.

  3. Authenticate yourself by creating a session:

    1. Expand Authentication and find POST /api/auth/admin/login.

    2. Click Try it out.

    3. Modify the request with your username and password.

    4. Click Execute.

    5. In the response, find X-MSTR-AuthToken and note the value. This value will be used in future steps.

  4. Export the database logins:

    1. Expand Datasource Management and find GET /api/datasources/logins/export.

    2. Click Try it out.

    3. In X-MSTR-AuthToken, enter the value you noted above.

    4. To export specific database logins, in the ids parameter, enter the database GUIDs, separated by a comma.

    5. To export all database logins, set includeAll to true.

    6. Click Execute.

      The result exports in JSON.

    7. Save the JSON response to a file (for example, dblogins_export.json).

      You will use the Strategy Gateway Agent user interface to import the logins, so you may need to copy the exported dblogins_export.json file to the location you will import.

Import Database Logins into Strategy Gateway Agent

  1. Open the Strategy Gateway Agent user interface in your browser.

  2. If prompted, authenticate yourself to the Library.

  3. Click the Database Logins tab and click Add.

  4. Navigate to the dblogins_export.json file and click Open.

  5. If there are no conflicts, wait for the import to finish. If there are conflicts, you will be prompted to Overwrite or Ignore the existing data.

Verify the Import

After the import successfully completes:

  1. Verify the vault configurations:

    1. In the Strategy Gateway Agent user interface, go to the Vaults section.

    2. Confirm the imported vaults display in the Vaults list.

    3. Click Test Connection.

  2. Verify the database logins:

    1. Go to the Database Logins section and confirm the imported logins display in the list.

    2. For vault-backed logins, verify they reference the correct vault.

  3. Test database connections:

    1. Use the imported database logins to connect to your data sources.

    2. Verify that connections succeed and data can be accessed.