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
It would be nice to be able to let semaphore use an external credential manager like OpenBao or HashiCorp Vault for secrets like SSH private keys, Ansible vault secrets and passwords. This would improve the security for the case that an attacker gets access to a backup of a machine running Semaphore UI. The attacker would not be able to use the credentials without access to the external secret manager.
Implementation
From my point of view the AccessKey struct in db/AccessKey.go needs an abstraction to retrieve the keys from an external secret manager or from the current implementation as a fallback. Configuration needs to be extended to configure the secret manager API endpoint as well as credentials (Token, Approle or potential other ways to authenticate against the secret manager).
Design
No response
The text was updated successfully, but these errors were encountered:
Related to
Ansible (task execution)
Impact
security improvements
Missing Feature
It would be nice to be able to let semaphore use an external credential manager like OpenBao or HashiCorp Vault for secrets like SSH private keys, Ansible vault secrets and passwords. This would improve the security for the case that an attacker gets access to a backup of a machine running Semaphore UI. The attacker would not be able to use the credentials without access to the external secret manager.
Implementation
From my point of view the AccessKey struct in db/AccessKey.go needs an abstraction to retrieve the keys from an external secret manager or from the current implementation as a fallback. Configuration needs to be extended to configure the secret manager API endpoint as well as credentials (Token, Approle or potential other ways to authenticate against the secret manager).
Design
No response
The text was updated successfully, but these errors were encountered: