I looked through GitHub and the .dev site and still have a few questions:
- Why isn’t OAuth delegation enough?
- Is this mainly for enterprise? If IT has already approved an agent for employees to use, what additional KYA/KYB problem still needs to be solved?
- Can you give a few examples of where this actually shows up in someone’s day-to-day use? That’s the part I’m struggling with most.
One suggestion: I’d spend more time on the sites explaining the “why” and the actual problem being solved, and a little less on the “how.” I think that would make it much easier to understand.
not OP but a couple related 'whys' that jumped out to me on their GH so curious your thoughts on them?
>OAuth2 Delegation & Consent. Manage OAuth2 scopes and user consent for third-party service integrations.
>MCP Servers for SaaS. If you want to offer an MCP server to your customers as part of your SaaS, the identity broker can provide an additional consent surface that records which agents were actually used. With centralized tool authorization, you can keep an audit trail of approvals on your side regardless of which agent the customer runs.
Thanks for sharing, and congrats on the launch.
I looked through GitHub and the .dev site and still have a few questions:
- Why isn’t OAuth delegation enough?
- Is this mainly for enterprise? If IT has already approved an agent for employees to use, what additional KYA/KYB problem still needs to be solved?
- Can you give a few examples of where this actually shows up in someone’s day-to-day use? That’s the part I’m struggling with most.
One suggestion: I’d spend more time on the sites explaining the “why” and the actual problem being solved, and a little less on the “how.” I think that would make it much easier to understand.
not OP but a couple related 'whys' that jumped out to me on their GH so curious your thoughts on them?
>OAuth2 Delegation & Consent. Manage OAuth2 scopes and user consent for third-party service integrations.
>MCP Servers for SaaS. If you want to offer an MCP server to your customers as part of your SaaS, the identity broker can provide an additional consent surface that records which agents were actually used. With centralized tool authorization, you can keep an audit trail of approvals on your side regardless of which agent the customer runs.
How would it handle transitive cases?