Skip to content

Pass the csharpDialog authorisation key to the progress dialog - #63

Merged
rodchristiansen merged 1 commit into
mainfrom
feature/dialog-auth-key
Oct 8, 2026
Merged

rodchristiansen merged 1 commit into
mainfrom
feature/dialog-auth-key

Conversation

@rodchristiansen

Copy link
Copy Markdown
Contributor

Closes #62

  • New DialogAuthKeyPath setting (policy, machine settings, ADMX/ADML), default C:\ProgramData\ManagedNotifications\authkey.
  • DialogAuthKey.Resolve: caller's DIALOG_AUTH_KEY first, else the trimmed key file; a missing or unreadable file means no key.
  • DialogManager sets the key in this process's environment only for the shell-executed launch (a shell-executed child inherits the environment and cannot be given its own), then restores it. Never on the command line or in the log.
  • If the dialog exits 30 within three seconds, a warning is logged and the run continues without the dialog.
  • Tests: DialogAuthKeyTests (4). dotnet test 126/126 pass.

When csharpDialog is managed with an authorisation key it exits 30 unless the
caller passes the plain key in DIALOG_AUTH_KEY. BootstrapMate now passes its
own DIALOG_AUTH_KEY through, or reads the key from the file named by the new
DialogAuthKeyPath setting (policy, machine settings or ADMX; default
C:\ProgramData\ManagedNotifications\authkey). The key goes only into the
dialog's environment, never the command line or the log. A dialog that
refuses the key is logged as a warning and the run continues headless.

Closes #62
@rodchristiansen
rodchristiansen merged commit 64d1346 into main Oct 8, 2026
2 checks passed
@rodchristiansen
rodchristiansen deleted the feature/dialog-auth-key branch October 8, 2026 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pass the csharpDialog authorisation key when launching the progress dialog

1 participant