Skip to content

Redact Authorization header from signJWT debug logs - #536

Open
diegoDrp-Dev wants to merge 1 commit into
google-github-actions:mainfrom
diegoDrp-Dev:fix/redact-signjwt-debug-token
Open

Redact Authorization header from signJWT debug logs#536
diegoDrp-Dev wants to merge 1 commit into
google-github-actions:mainfrom
diegoDrp-Dev:fix/redact-signjwt-debug-token

Conversation

@diegoDrp-Dev

@diegoDrp-Dev diegoDrp-Dev commented Aug 23, 2026

Copy link
Copy Markdown

Prevents the access token used by signJWT() from being included in debug logging.

The request continues to use the original Authorization header, while a sanitized copy of the headers is passed to the logger.

This also adds a regression test verifying that:

  • the real bearer token is sent to the HTTP client;
  • the token is not passed to the logger;
  • the logged Authorization header is redacted;
  • signJWT() behavior remains unchanged.

Related Google Issue Tracker report: 550959018

Validation:

  • npm test: 55/55 passing
  • npm run lint: passing
  • npm run build: passing
  • git diff --check: passing

@diegoDrp-Dev
diegoDrp-Dev requested a review from a team as a code owner August 23, 2026 04:13
@google-cla

google-cla Bot commented Aug 23, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@diegoDrp-Dev
diegoDrp-Dev force-pushed the fix/redact-signjwt-debug-token branch from 0879f09 to 197b22b Compare August 23, 2026 04:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant