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
  3. KB489583: Passing System Prompts on Library Trusted Authentication

KB489583: Passing System Prompts on Library Trusted Authentication


Menglu Xia

Product Owner, Principal • MicroStrategy


Starting in Strategy One (November), trusted authentication supports passing system prompts through headers.

The following 2 trust headers were introduced:

mstr-system-prompts

A base64 JSON string consist of key-value pairs: the key is the system prompt index as a number string, and the value is the associated system prompt value. System prompt values should be utf8 encoded

See the following example:

mstr-system-prompts: eyI1OSI6ICJIZWxsbyB3b3JsZCIsICI2MCI6ICJMaW5lMQpMaW5lMiIsICI3NCI6IDQ1LCAiODkiOiAiMjAyNS0xMC0xMCJ9

The value above could be decoded as the following:

{
 "59": "Hello world",
 "60": "Line1\nLine2\nLine3",
 "74": 45,
 "89": "2025-10-10"
}


mstr-persist-system-prompts

A boolean string of either "true" or "false" indicates if the system prompt should be used on the server or locally in the current session. The default value is "true". The flag will have no effect is no system prompt is passed through login.

See the following example:

mstr-persist-system-prompts: false

 

See the following list of system prompts that is available to trusted authentication:

Category

Index range

Data type

ESM system prompts

54, 55

text

56

number

57

date

58

big decimal

SSO system prompts

59~73

text

74~88

number

89~98

date

When constructing mstr-system-prompts header, ensure to follow the below best practices:

  • Ensure the JSON key/values are UTF-8 encoded before Base64 conversion.
  • Keep the total header size under 8 KB to stay within server and proxy limits.
  • Include only necessary prompts to reduce payload.
  • Escape special characters properly in text prompts.
  • Use ISO-8601 format (YYYY-MM-DD) for date prompts.

Comment

0 comments

Details

Knowledge Article

Published:

December 16, 2025

Last Updated:

December 16, 2025