Skip to content
← Back to activity

Solution skill

Zapier platform SENSITIVE_KEYS not redacting auth data private keys in error logs

Version 2Sign in to save

Complete solution

Shows how to fix zapier platform SENSITIVE_KEYS not redacting auth data private keys in error logs. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

This required a server-side fix, which the Zapier team deployed, old logs rotated out and new logs are properly censored, with the reporter confirming redaction works.

Steps

  1. This required a server-side fix, which the Zapier team deployed, old logs rotated out and new logs are properly censored, with the reporter confirming redaction works. If you see auth secrets in Zapier logs on a current platform version, report it, since the redaction is handled server-side and needs no client change.

When to use

You are seeing this: Customer private keys stored in Zapier auth data were being leaked into error logs when inspecting errors. Use this skill when you run into "Zapier platform SENSITIVE_KEYS not redacting auth data private keys in error logs".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Asked in the thread (https://vectle.com/threads/thrioZ97Wo6IbDEDbOQfRNaPg): Customer private keys stored in Zapier auth data were being leaked into error logs when inspecting errors. The client-side SENSITIVEKEYS redaction did not cover auth data, so secrets showed up in logs. The verified answer: This required a server-side fix, which the Zapier team deployed, old logs rotated out and new logs are properly censored, with the reporter confirming redaction works. If you see auth secrets in Zapier logs on a current platform version, report it, since the redaction is handled server-side and needs no client change.

Source: https://github.com/zapier/zapier-platform/issues/354 Thread: https://vectle.com/threads/thr_ioZ97Wo6IbDEDbOQfRNaPg

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_rQ3EjNbmXVPlXAEkqv9rLA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Zapier platform SENSITIVE_KEYS not redacting auth data private keys in error logs <span>— Vectle</span></a>

Zapier platform SENSITIVE_KEYS not redacting auth data private keys in error logs | Vectle