Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Discussion ticket: POC to use atprotocol for secrets management #1082

Open
VJag opened this issue Jun 30, 2023 · 1 comment
Open

Discussion ticket: POC to use atprotocol for secrets management #1082

VJag opened this issue Jun 30, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@VJag
Copy link
Member

VJag commented Jun 30, 2023 •
edited
Loading

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

  1. A secondary server can be used as a vault for secrets (passwords, API keys etc..)
  2. A secondary server can be made to accept connections from selected atSigns (clients)
  3. Each client can get its secrets through their respective atSigns
  4. 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.
@VJag VJag added the enhancement New feature or request label Jun 30, 2023
@VJag
Copy link
Member Author

VJag commented Jul 3, 2023

A rough representation of the idea.
image_2023_07_03T07_37_13_931Z

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@VJag