Repository navigation
Replies: 2 comments
|
worried if someone crack paper click |
0 replies
|
I had this same idea yesterday: integrating 1Password. I'm going to work on it, and if it's successful, I'll share it here. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Paperclip currently stores agent secrets in its own database. It would be useful to also reference secrets held in an external manager: 1Password (via Connect or service accounts), HashiCorp Vault, Bitwarden Secrets Manager, or a cloud provider’s secret store. A secret_ref could point at a provider instead of a copy kept in Paperclip, and the value would be resolved only at run time, when it’s injected into the agent’s environment. That keeps one source of truth, so rotating a credential in the vault updates every agent with no second copy to forget. Secrets also never sit at rest in the Paperclip database or its backups. And access is governed and audited by the tool the rest of the household or company already uses. A per-secret cache TTL and a clear error when the provider is unreachable would make it practical for self-hosted setups.
All reactions