Repository navigation
Description
Summary
A long-running aac listen --reusable-psk LaunchAgent daemon on macOS enters a persistent "Credential request failed: Request denied" state for ALL remote-client credential requests after a host reboot, even though:
- PSK state file (
~/.access-protocol/psk_store_user_client.json) survives reboot intact - Listener identity (
user_client.key) unchanged - Fresh BW_SESSION loaded post-reboot (BW CLI unlocked successfully)
- Listener process re-runs cleanly and reports
state = running
The denial is preceded by a specific warning pattern at ap_client::clients::remote_client:
INFO aac::command::connect: Requesting credential for domain: council.hermes.foo
WARN ap_client::clients::remote_client: Ignoring response with mismatched request_id: Some("req-NNNNNNNNNNN-xxxxxxxx")
ERROR aac::command::run: Credential request failed: Request denied
The remote-client receives A response from the proxy but with a different request_id than the one it sent — the client correctly ignores it, then times out waiting for its own response, surfacing as "Request denied" (caught by #141's ambiguous-denial-class).
Environment
- aac version: 0.11.0 (commit
3b000d15af71be5ddcf8893b099f3a66d386be9d) - macOS Tahoe (aarch64)
- Deployment:
aac listen --reusable-psk --provider bitwarden -vunder/usr/bin/script -q /dev/nullPTY wrapper, invoked by a macOS LaunchAgent - Bitwarden CLI: current
@bitwarden/cli - Proxy:
wss://ap.lesspassword.dev(default)
Timeline
- T-103d — initial
aac connect --tokenpairing ceremony completed via operator at TUI. Listener + remote-client state established.connection_cache_user_client.json+connection_cache_remote_client.jsonpopulated. All subsequent credential requests served GREEN for 103 days. - T-14d — host reboot (macOS scheduled restart).
- T-13d — post-reboot: aac_listen daemon restarts cleanly, BW_SESSION re-provisioned, PSK store intact. BUT all council.* domain credential requests from LaunchAgent-driven daemons return "Request denied" with
request_idmismatch warning. - T-0 — 13+ days of persistent crash-loop (
KeepAlive=trueLaunchAgent re-fires every ~30s, each attempt denied).
Repro shape
After a host reboot on a previously-paired aac listen --reusable-psk daemon:
- Verify PSK state intact:
jq . ~/.access-protocol/psk_store_user_client.jsonshows 1 entry with pre-rebootcreated_at. - Verify listener paired:
aac connections listshowsPaired: Nmonths ago | Last used: Nmonths ago. - Trigger credential request from a remote-client (e.g., a LaunchAgent-driven daemon running
aac run --domain some.domain --env X=password -- somecmd). - Observe
aac listenlog (viatail -f ~/ops/aac_listen.logwith ANSI strip):INFO aac::command::connect: Requesting credential for domain: some.domain WARN ap_client::clients::remote_client: Ignoring response with mismatched request_id: Some("...") ERROR aac::command::run: Credential request failed: Request denied
What we verified does NOT resolve
- Re-establishing BW_SESSION (fresh
bw unlock+ Keychain refresh) — no change - Bootstrap/bootout cycle of the LaunchAgent — no change
- Attempted full re-pair (wipe
~/.access-protocol/+ freshaac listen+aac connect --token <NEW>) — blocked at a different failure class: new-domain approval requires TUI per the headless-LaunchAgent-denies-fresh-domains class, so headless re-pair is architecturally dead (separate class)
Hypothesis
Proxy-side session state at wss://ap.lesspassword.dev appears to track "listener online since " with some TTL or heartbeat semantic. A 24-hour-plus gap between pre-reboot listener-online and post-reboot listener-online causes proxy-side pairing expiry OR some request_id mapping desync. The client-side PSK + identity + cached connection all survive, but proxy no longer routes responses with matching request_ids.
Related to #161 but subtler: in our case the proxy DOES respond; it just responds with request_ids the client doesn't recognize.
Expected behavior
Either:
- Proxy-side session should refresh transparently on listener reconnect (make reboot transparent)
- OR listener should detect proxy-side desync via first request/response cycle and re-pair automatically
- OR there should be a documented recovery procedure for post-reboot proxy-desync class
Diagnostic info we can provide
If helpful, we can share (sanitized):
- Full log excerpts of the denial cycle
aac connections list -voutput showing paired fingerprints- Timing of reboot vs first denial
- Repro command set
References
- Consumer receives bare "Request denied" for all failure modes (locked vault, not found, explicit deny) #141 — Consumer receives bare "Request denied" for all failure modes (relates to diagnostic surface)
aac run/aac connecthang indefinitely when the relay accepts the connection but never responds;--timeoutdoes not apply #161 —aac run/aac connecthang indefinitely when the relay accepts the connection but never responds (similar class · subtler symptom here)
Thanks for maintaining the project. Happy to help repro or provide additional diagnostics.
Activity
bitwarden-bot commentedon Nov 17, 2026
Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-47124
Link (for internal use): https://bitwarden.atlassian.net/browse/PM-47124
dmorriss-bw commentedon Nov 17, 2026
Hello @jimmikroo
Thank you for your report. I have flagged this to the Engineering team for review; please feel free to post additional information, such as screenshots or a screen video recordings, if you wish.
Thank you again,