Deploying and administering
Credential and Active Directory model
How Muon Insight uses Windows identity, stored credentials and Active Directory.
For Muon Insight 0.26.0. This guide also ships inside the app under Help and Documentation.
Credential profiles are a Phase 3 service behind a CredentialStore abstraction. Production Windows
implementation writes secrets to Credential Manager under the current user and may use DPAPI for
additional local metadata. Configuration stores only a non-secret profile identifier/display name.
The core transport obtains a secret for the shortest possible interval, constructs a secure in-memory
credential, and never passes plaintext to a module or command-line argument. Session and one-time
credentials are cleared on request and shutdown.
Authorization uses current-token groups where possible. Windows expands nested domain group membership into the logon token; access changes require token refresh/sign-in. The policy maps configurable domain groups to application/navigation/module/action/update/development capabilities. Denied groups take precedence. Offline default is read-only; production may choose deny or protected cached authorization with expiry and DPAPI integrity. Every denial is logged and explained without disclosing sensitive group details.
Something wrong or unclear? Open an issue on GitHub.