RFC: OAuth 2.0 Flow Management

[marvindanig]

Hey folks 👋

We’re considering Jentic Mini as our credential + broker layer for a multi-tenant SaaS product. The vault/broker architecture looks like a great fit, and the Apache 2.0 license is a big reason we’re evaluating it.

One gap we’ve identified is OAuth 2.0 lifecycle support. Many integrations we need (Google, Slack, HubSpot, Salesforce, etc.) require full OAuth — redirect, callback, token exchange, and refresh rotation. Token storage is covered well, but the OAuth lifecycle itself doesn’t appear to be handled end-to-end yet.

We’d be open to contributing an OAuth module, potentially including:

• provider registry (~20 providers)
• authorization + callback endpoints
• token exchange / refresh handling
• refresh worker / daemon
• integration with the existing broker / vault pattern

Wanted to check first:

1. Is OAuth support already on the roadmap?
2. Would a contribution of this scope be something you’d be open to reviewing?
3. Would you prefer one larger PR or a phased series?

Happy to write up a short design doc / RFC first if useful.

Thanks!

[marvindanig]

I have my answer. Thanks!

[MichaelCordner]

Sincere apologies, I just happened to see this now. We're monitoring issues as they come up, but discussions aren't getting flagged for some reason and it got lost in the noise. Again, sorry about that.

Yes, this is absolutely on the roadmap and something we'd be happy to work together on. I opened a similar issue here and it's something we'd be happy to proritize:

#104

Rather than PRs, we're trying to operate this project by spending time up-front speccing issues, which we're then feeding into a development harness to implement and test. If you could take the time to add your reqirements and thoughts to the existing issue, we'll work with you to get them implemented ASAP.

[marvindanig]

Sounds good. I'll take a pass at it this week. 🙏🏻