FRESH

Hacker News

Show HN: OneCLI – OSS credential gateway that keeps secrets out of AI agents

49 points by Jonathanfishner

by sandeepkd

1 subcomments

It works great for static credentials. As a product I think about adding couple more things that might be helpful here (Btw I am not the client for this, I just happen to know them as practical problems)
1. Support for OAuth Client credentials - Gateway does the OAuth dance to get the access token, this is quite practical and even useful in case of regular services running across clusters and sharing the same clientId-secretId
2. Support for request retries on certain failures and short circuiting in other cases

by emilsoman

0 subcomment

by redbridgerock

0 subcomment

by doctorpangloss

1 subcomments

by stephantul

1 subcomments

It is hilarious to see most comments are people peddling their own products more or less directly.

by notaharvardmba

1 subcomments

oauth, saml, oidc accomplish the same thing in a way more mature way, so if you’re already using SSO just do that instead of adding another point of failure..

by winterrx

1 subcomments

nice launch. i have started to use a secrets manager (infisical) recently for my different projects and it's been really helpful. are your customers solo hackers, small startups or large enterprises that are looking for this kind of solution? i like to see competition in the space

by theozero

0 subcomment

Looks great. The "credential broker" pattern (inject placeholders, replace in proxy) is something we just added to https://varlock.dev (totally free and open source).
Rather than using a dashboard, ours is configured within a .env.schema file, and rather than our own vault, we can pull secrets using our plugins (16 and counting) including Infisical, 1Password, Bitwarden, AWS, GCP, Azure, more. Also very useful for coding tasks in general, as we have integrations for most frameworks, and add built in validation, type safety, leak detection, etc.
Will definitely be keeping an eye on OneCLI to compare notes.

by denysvitali

0 subcomment

Nice! I've built something like this, although specific to GitHub: https://github.com/denysvitali/gh-proxy
The idea being that if the fake token leaks from my sandbox - it would be completely useless for an attacker

by rahulr0609

0 subcomment

+1 to Infisical.
We added Hashicorp Vault support here: https://github.com/Infisical/agent-vault/pull/256

by adithyassekhar

2 subcomments

Holy mother of whatever this is, everyone got the same idea again and there’s a bunch of implementations people are desperate to promote in the comments.
You’re just trading one key for another, whatever abstraction you chose to trust, at some point credentials will pass to your llm of the week.