11–20 of 47 posts
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.
How?
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.
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
does the agent control the environment that onecli is running in? (yes)
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 clientI…
1. we support OAuth apps today, and we're growing the catalog based on demand. we support rotating and refreshing tokens for those.
2. I'd like to understand your case better. sitting in the request path means we could own retry mechanisms, but I'm curious what made you think of it, what kind of use cases did you have in mind?
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 clientI…
thanks, both are useful. 1. we support OAuth apps today, and we're growing the catalog based on demand. we support rotating and refreshing tokens for those. 2. I'd like to understand your case better. sitting in the request path means we could own retry mechanisms, but I'm curious what made you think of it, what kind of use cases did you have in mind?
Trip breaker patterns are good for resource usage on both sides (client and server) when you know things are not working. In addition to that it also saves on cost for the clients if every call is billed irrespective of success or failure.
It is hilarious to see most comments are people peddling their own products more or less directly.
"Build it and they will come" now works well for competition:
- If you build it (and it is not useful) they won't come.
- If you build it (and it is useful and successful) they will come and copy you to build their own.
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..
No they don't - you're still giving the agent a static token that can be exfiltrated and used elsewhere.