Secure identity propagation and the app host path
Domino uses theSecureIdentityPropagationToAppsEnabled feature flag to control how requests are routed to a running app. When the flag is true, Domino changes the URL routing structure it uses to proxy requests.
Defaults by version:
Symptoms of an incompatible app
An app that manually constructs its path prefix fromDOMINO_PROJECT_OWNER, DOMINO_PROJECT_NAME, and DOMINO_RUN_ID produces a path that no longer matches the new routing structure. The app continues to run until it is restarted, then fails on the next start.
Common symptoms:
- Blank page, 404, or 502 after restart.
- Dash (Plotly) app fails to serve assets or callbacks.
- The app worked before the flag was enabled or before the last restart.
Update your app to use DOMINO_RUN_HOST_PATH
Replace any manually constructed path prefix with the Domino-provided DOMINO_RUN_HOST_PATH environment variable. Domino sets this variable automatically and it always reflects the correct routing path, regardless of the flag state.
Before (breaks when the flag is true):
Any Python web framework that accepts an explicit base path or prefix (Dash, Streamlit, Flask, and others) should read the prefix from
DOMINO_RUN_HOST_PATH.Next steps
- Apps in Domino gives an overview of how apps work within the Domino ecosystem.
- Publish and deploy App versions explains how publishing a version differs from deploying it, and which settings you can change without creating a version.
- Learn more about how Apps in Domino run and what identity and permissions are used.