Skip to content

[Feature] Allow setting custom JWT secret through a flag or environment variable #3745

@hrishikesh-k

Description

@hrishikesh-k

Is your feature request related to a problem? Please describe:

Based on this PR, users can now set custom JWT secret to get RBAC working locally. The problem is that, if users wish to keep the same JWT secret in their production and CLI environment, they don't have a good way to do this safely. If they add the secret to their netlify.toml, there's a good chance that this will go to their remote repository and be exposed.

Describe the solution you'd like:

Allowing users to set the JWT secret as a flag in the command would be one option. Another option would be to let users save this secret as an environment variable in their .env file or something similar. In most cases, that file is not pushed to a remote repository. Additionally, since CLI is able to pull variables set it the UI, users could simply set it in their UI to avoid leaking it to their repository.

Describe alternatives you've considered:

None

Additional context:

N/A

Can you submit a pull request?

No

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions