This website uses cookies to ensure you get the best experience.
Learn more.
A workflow log redacts an API token, but a later script encodes that token and prints the encoded value. Why is this still a security problem?
Published
- A redacted earlier step makes the entire subsequent job log private to the workflow author.
- Only the literal secrets context can contain sensitive data.
- Encoding permanently revokes the original token.
- Avoid logging credential transformations and mask any derived sensitive values when needed.
Comments — 0
Sign in to comment