Discussion ticket: POC to use atprotocol for secrets management
VJag opened this issue · comments
Is your feature request related to a problem? Please describe.
I believe a solution around atProtocol will be a cost-efficient solution for secrets management.
Describe the solution you'd like
- A secondary server can be used as a vault for secrets (passwords, API keys etc..)
- A secondary server can be made to accept connections from selected atSigns (clients)
- Each client can get its secrets through their respective atSigns
- Change in secrets can be propagated to the clients using reshare/notification
Describe alternatives you've considered
No response
Additional context
We might be discussing SSHNoPorts with the dev operations community; this could be yet another idea we can propose.
A rough representation of the idea.
