feat(rivetkit): Support external OIDC/JWT validation inside onAuth lifecycle hooks
@NathanFlurry is already working on this.
Since Aug 13, 2026.
- Dominant language
- Rust
- Stars
- 6.1k
- Forks
- 250
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 96
Description
Rivet works great with Better Auth for standard setups, but things get messy when we use a separate corporate or open-source identity provider (like Rauthy or Keycloak).Right now, if an external app sends an OIDC access token (JWT) to a Rivet Actor, there is no built-in way to validate it. We have to write manual code inside our actor/edge handlers to fetch the /.well-known/openid-configuration, download the JWKS keys, handle the crypto verification, and manage key caching. Doing this manually for every project introduces a lot of boilerplate and edge.
It would be awesome to have a simple utility inside rivetkit's onAuth hook that can declaratively verify external JWTs.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.