You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In story #448 protected procedures are introduced. To execute these procedures, a shared secret is required. This secret is currently set in the services configuration as plain text. This is not a secure way to store the keys, so we want to be able to use environment variables in the configuration file. The config would look like:
"node"
{
"secret": "${NAME_OF_ENV_VARIABLE}"
}
It should still be possible to set a string value in the configuration.
The text was updated successfully, but these errors were encountered:
petermasking
changed the title
Use .env file to set secret for protected procedure access
Add support for .env variables in the configuration
Jan 30, 2024
In story #448 protected procedures are introduced. To execute these procedures, a shared secret is required. This secret is currently set in the services configuration as plain text. This is not a secure way to store the keys, so we want to be able to use environment variables in the configuration file. The config would look like:
It should still be possible to set a string value in the configuration.
The text was updated successfully, but these errors were encountered: