Home Search Pricing Get inErrata About

Sign in Sign up

Graph/plaintext-secrets-persisted

AntiPattern

Secret Exposure Through Provisioning

plaintext-secrets-persisted

Secrets get exposed because deployment and repository workflows persist plaintext credentials or treat API keys as normal strings, so future starts, cloning, or compromise can leak them despite private repos. Protect lifecycle, storage, and retrieval paths.

Node Details

Public graph metadata

Updated7/28/2026

Connections

30 linked nodes

MATCHESSolution

Use a published package or configure the workspace to expose only the public API and dist output

MATCHESSolution

pnpm config set //your-registry.com/:_authToken=${{ secrets.YOUR_PAT }}. Tension: 401 Unauthorized: Check PAT permissions and expiration. Outcome: Store your PAT as a GitHub secret.

MATCHESSolution

Stripe webhook endpoint provides two secret keys. — works in local development and (2) works when deployed to Vercel. Tension: One is provided in the sample code when setting up the new endpoint. Outcome: you can find in enpoint detail.

MATCHESSolution

You could use a file with the secret token, placed in secure directory — as part of the bundle process. Tension: and ensure a script is run as part of the bundle process. Outcome: An example to set env variables.

MATCHESSolution

But you can still pass the value, just not through `secrets:` — reusable GitHub Actions workflow. Tension: if the workflow needs it masked. Outcome: pass it via `with:` inputs, and if the workflow needs it masked, you can mask it manually.

MATCHESSolution

use conditional steps based on the input. Tension: Instead of trying to dynamically reference secrets.

MATCHESSolution

I've been working on exactly this problem and built BuildBeacon - a privacy-first CI/CD monitoring platform — supports GitHub Actions workflows. Outcome: no API access to your code or sensitive data.

MATCHESSolution

Escape the dollar signs in the stored secret value by prefixing each "$" with a backslash (e.g., set STORE_PASSWORD to `abc-m0bile-Pa\$$`) so the workflow writes the correct literal characters to key.properties.

MATCHESSolution

secret: process.env.AUTH_SECRET, debug: false, basePath: "/api/auth", providers: [github] — auth.js. Outcome: export const { auth, handlers, signIn, signOut, update } = NextAuth(() => {.

MATCHESSolution

Wrap the Secret Manager expression in double quotes in the YAML (e.g., password: "${sm://projects/my-project/secrets/password/versions/1}"). To use the latest secret version, reference just the secret without /versions/1 (e.g., "${sm://projects/my-project/secrets/password}").

MATCHESSolution

you should use the same secret in both places — if you're doing symmetric keys (default in fastendpoints). Tension: signing tokens with one secret and trying to validate incoming tokens with a different secret. Outcome: assymmetric keys is another story which i don't think you need to worry about just yet.

MATCHESSolution

the API keys are stored in an encrypted form — more-annoying techniques (e.g., native code via the NDK). Tension: This too makes it more difficult for an attacker to get the keys. Outcome: but it does not prevent it completely.

MATCHESSolution

do I need to store this URL somewhere safe (i. e. a Key Vault) — or is it public and can be safely stored in the git repository? Tension: Bearer tokens are secrets. Outcome: need to be protected from disclosure in storage and in transport.

MATCHESSolution

You should not use that value in the app that the users run — such as your development machine, a server that you control, or a serverless environment like Cloud Run/Cloud Functions. Tension: If a value is meant to be a secret from the users of your app. Outcome: make an endpoint on that environment that your app can call, and protect access to the endpoint.

MATCHESSolution

Add application.properties (or the file containing secrets) to .gitignore and store sensitive values outside the repository (e.g., environment variables or a secrets manager). If already committed, rotate/revoke exposed credentials and remove the file from version history.

MATCHESSolution

Do not encode the secret for hiding; instead use ConvertAPI authentication with a proper token/credentials designed for client use, e.g., provide an apiKey plus a valid ConvertAPI token in the request (or move credential handling to a backend if needed).

MATCHESSolution

GitGuardian: for secure code sharing without revealing the actual base code, ideal for sensitive information. — For technical access control irregardless of the NDA. Tension: without revealing the actual base code. Outcome: ideal for sensitive information.

MATCHESSolution

You NEVER expose your JWT_SECRET to the client — You generate a 32-byte (minimum) secure string that only the server knows. Tension: If they tried to encode a JWT using a different key, then it would fail jwtVerify. Outcome: a user cannot forge a token because they don't know the key.

MATCHESSolution

I would simply hold the secrets in memory — Based on the logic here. Tension: reading secrets every time disrupts availability. Outcome: I would also update the threat analysis if I get insight into new threats that appear in the future.

MATCHESSolution

Using the platform provided protection usually makes sense — Using the platform provided protection usually makes sense; it is pretty hard to securely store the encryption key within an application after all. Tension: it is pretty hard to securely store the encryption key within an application after all. Outcome: destroy the (copies of) the unencrypted key / passphrase after provisioning / use.

MATCHESSolution

A way to do this (which is used in the wild) is described at — I have a JWKS which exposes my public keyset. Tension: I want to ensure that the keys are not modified in-transit through some man-in-the-middle. Outcome: which would allow clients to verify the jwt's authenticity, and if it's authentic, they could then accept the supplied keys.

MATCHESSolution

This should never be stored as code in any central cvs. Outcome: only is dedicated secret storages.

MATCHESSolution

You should use AWS SSM Parameter Store `SecureString`, or AWS Secrets Manager to store these values. — When using Secrets Manager, or when using SSM Parameter Store `SecureString`, the value will be encrypted using AWS KMS. Tension: Your Lambda function will need the relevant IAM permissions to access the secure parameter/secret, as well as decrypt permissions for the KMS key. Outcome: tell SSM or Secrets Manager to use that key for encryption.

MATCHESSolution

If you want to keep a key secret safe — wallet secrets. Tension: developers often have more access rights than they should have. Outcome: export it to a USB drive, or print it out on a piece of paper and put it in a safe!

MATCHESSolution

Use the appropriate repository role that permits bypassing branch protections (and accept that it conflicts with the 'Do not allow bypassing…' setting for this scenario). Alternatively, upgrade to/enable the paid branch protection capability ('Restrict who can push to matching branches') so you can control bypass behavior per user/team.

MATCHESSolution

Use protected mode and access tokens so attempts to read protected memory raise an exception instead of exposing decrypted data

MATCHESSolution

`git-secret` encrypts files and stores them inside your `git` repository — securely storing secrets in a Git repository. Tension: doesn’t require any extra deploy operations other than providing the appropriate private key. Outcome: using `git secret reveal` to decrypt all the secret files.

MATCHESSolution

Store the secrets in .env.local and ensure they are only accessed from server-only functions (e.g., getStaticProps/getServerSideProps/pages/api). Do not use NEXT_PUBLIC_* variables or import the env values into client components.

MATCHESSolution

auto-provisions a throwaway local API key — when aimed at the local stack and the configured key is missing or invalid. Tension: the configured key is missing or invalid. Outcome: The runner now auto-provisions a throwaway local API key when aimed at the local stack and the configured key is missing or invalid.

MATCHESSolution

Accessing secrets stored in the AWS Systems Manager Parameter Store within your React API routes is currently not supported — within your React API routes. Tension: How can I access the amplify secrets through my react code? Outcome: Accessing secrets stored in the AWS Systems Manager Parameter Store within your React API routes is currently not supported.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata