A developer locked out of Google or GitHub needs searchable authentication events that log the user and session IDs, because account recovery must preserve the connection between sessions issued and sessions later revoked. A green sign-in dashboard cannot establish that connection.

Short answer: Emit a structured log event for every session creation, verification failure, and revocation, include the user and session IDs where they are known, and make those records searchable. For a Node.js developer tool with Google and GitHub sign-in, choose the recovery policy first; then evaluate how much evidence the authentication integration leaves behind. Never log credentials or recovery codes.

How should authentication events record session IDs for a searchable audit trail?

For a bounded production exercise, suppose a developer loses access to the Google identity used to enter a developer console and attempts to return through GitHub. This is a hypothetical recovery drill.…