Skip to content

Improvement - Prevent Unicode and special-character keys in secret imports and modals #4882

@LEMINHMAN1

Description

@LEMINHMAN1

Feature description

Improve secret key validation for all import formats (.env, .json, .yml) to prevent users from creating secrets with Unicode or special-character keys.
Only allow ASCII-safe keys:
A–Z a–z 0–9 . _ -

Invalid keys should be rejected or highlighted with a tooltip warning.

Why would it be useful?

Unicode and special characters in secret keys are not supported by most platforms, including:

AWS Lambda / ECS / Parameter Store
Docker
Kubernetes env vars
GitHub Actions
Vercel / Netlify / Render

These keys cannot be mapped into environment variables and often cause deployment failures or missing secrets.
Validating them early prevents confusing production issues.

Additional context

  • Should prevent users from including JSON or .env files that contain invalid keys in the "Paste Secret Values" modal.
Image
  • When users enter an invalid key in the "Add secret key" modal, a warning should be displayed to let the user correct it.
Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions