No Browser Secrets
Switching happens through backend profile IDs. Mirth usernames, passwords, and tokens are never sent back to the browser.
Mirth Server Profiles
Persistent per-user targets for Mirth, BridgeLink, test, stage, prod, and DR. Credentials stay encrypted on the backend.
Credential Encryption
Stored credentials are encrypted before writing to local runtime data. Production should set MIRTH_PROFILE_ENCRYPTION_KEY.
Active Context
Changing the active server reloads live data so channels, messages, users, events, templates, and settings follow the selected target.
dev
Local Dev
https://127.0.0.1:8443
- Credentials
- missing
- TLS Verify
- enabled
- Database
- none
- Profile
- env
test
Test Ubuntu
https://test-mirth.example.local:8443
- Credentials
- missing
- TLS Verify
- enabled
- Database
- readonly
- Profile
- env
prod
Production Primary
https://prod-mirth-01.example.local:8443
- Credentials
- missing
- TLS Verify
- enabled
- Database
- readonly
- Profile
- env