Root cause of every failed browser sign-in: the companion runs elevated, and PipeOptions.CurrentUserOnly keyed the callback inbox to the elevated token's default owner (Administrators). The protocol handler the browser launches runs as the ordinary user with Administrators as a deny-only group, so it was refused with "Access to the path is denied" before reaching the app.
The inbox is now created through NamedPipeServerStreamAcl with an explicit descriptor: owner and single allow rule set to the user's own SID. The handler's client drops the owner comparison and relies on the existing process-image verification of the companion.
New tests: inbox descriptor shape, and a forwarded-callback round trip through the handler's client path.
Version 1.1.1; CHANGELOG updated. No wire change.
Verification
NativeCI solution: zero warnings. Qqq.PrintAgent.Cli.Tests: 351 passed.
Reproduced on the dev PC: unelevated connect to the inbox failed with access denied under the old descriptor; the forwarded-callback test passes with the new one. Installed acceptance of a full browser sign-in follows with the local 1.1.1 MSI.
Substantial AI assistance was used for this change.
## Summary
- Root cause of every failed browser sign-in: the companion runs elevated, and `PipeOptions.CurrentUserOnly` keyed the callback inbox to the elevated token's default owner (Administrators). The protocol handler the browser launches runs as the ordinary user with Administrators as a deny-only group, so it was refused with "Access to the path is denied" before reaching the app.
- The inbox is now created through `NamedPipeServerStreamAcl` with an explicit descriptor: owner and single allow rule set to the user's own SID. The handler's client drops the owner comparison and relies on the existing process-image verification of the companion.
- New tests: inbox descriptor shape, and a forwarded-callback round trip through the handler's client path.
- Version 1.1.1; CHANGELOG updated. No wire change.
## Verification
- NativeCI solution: zero warnings. `Qqq.PrintAgent.Cli.Tests`: 351 passed.
- Reproduced on the dev PC: unelevated connect to the inbox failed with access denied under the old descriptor; the forwarded-callback test passes with the new one. Installed acceptance of a full browser sign-in follows with the local 1.1.1 MSI.
Substantial AI assistance was used for this change.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
PipeOptions.CurrentUserOnly keyed the inbox to the elevated token's default owner
(Administrators), so the unelevated protocol handler was refused and no browser sign-in
could complete. The inbox now carries an explicit descriptor owned by and restricted to the
user's SID; the handler verifies the companion by process image instead of the owner check.
Adds inbox security and round-trip tests. Version 1.1.1.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
PipeOptions.CurrentUserOnlykeyed the callback inbox to the elevated token's default owner (Administrators). The protocol handler the browser launches runs as the ordinary user with Administrators as a deny-only group, so it was refused with "Access to the path is denied" before reaching the app.NamedPipeServerStreamAclwith an explicit descriptor: owner and single allow rule set to the user's own SID. The handler's client drops the owner comparison and relies on the existing process-image verification of the companion.Verification
Qqq.PrintAgent.Cli.Tests: 351 passed.Substantial AI assistance was used for this change.
🤖 Generated with Claude Code