Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLIPublic
Assigneesstack72

Relationships

#2057 Audit: emit auth-category events for OAuth device flow and token operations

Opened by stack72 · 9/8/2026· Shipped 9/8/2026

The device auth handler (src/serve/device_auth_handler.ts) completes OAuth logins, admission checks, and token minting without emitting any audit events. These are security-critical operations that should appear in the audit log under the auth category.

Currently no handler in the serve pipeline uses the auth audit category — it exists in the AuditCategory type but nothing emits it.

Events to add:

  • auth.login.started — device grant initiated
  • auth.login.completed — OAuth flow completed, token minted (success)
  • auth.login.denied — admission check failed (denied)
  • auth.login.expired — device code expired
  • auth.token.revoked — token revocation (if not already audited)

The device auth handler runs in the HTTP request path, not the WebSocket handler pipeline, so the auditEmitter needs to be threaded through DeviceAuthDeps.

Discovered during Phase 3 (issue #2049) dashboard testing — the Activity page shows no auth-category events.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 7 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

9/8/2026, 6:00:02 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack729/8/2026, 3:58:31 PM

Sign in to post a ripple.