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
From OpenSSL silver badge requirements: The project MUST support storing authentication credentials (such as passwords and dynamic tokens) and private cryptographic keys in files that are separate from other information (such as configuration files, databases, and logs), and permit users to update and replace them without code recompilation. If the project never processes authentication credentials and private cryptographic keys, select "not applicable" (N/A)
We are compliant with this requirement with the exception that we have no supported mechanism to force a credential rotation.
Describe the solution you'd like
Enhance the secrets-config utility to support forced credential rotation:
Redis password
MQTT password
Vault master key?
Consul tokens?
JWT signature keys?
The text was updated successfully, but these errors were encountered:
bnevis-i
changed the title
Enable forced credential rotation in secrets-config utility
Enable forced credential rotation in secrets-config utility [ossf silver]
Nov 7, 2022
🚀 Feature Request
Relevant Package [REQUIRED]
secrets-config utility
Description [REQUIRED]
From OpenSSL silver badge requirements:
The project MUST support storing authentication credentials (such as passwords and dynamic tokens) and private cryptographic keys in files that are separate from other information (such as configuration files, databases, and logs), and permit users to update and replace them without code recompilation. If the project never processes authentication credentials and private cryptographic keys, select "not applicable" (N/A)
We are compliant with this requirement with the exception that we have no supported mechanism to force a credential rotation.
Describe the solution you'd like
Enhance the secrets-config utility to support forced credential rotation:
The text was updated successfully, but these errors were encountered: