github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 06:16:18 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

OAuth 2.1 Provider - Back-Channel Logout #2936

New Issue
Open
opened 2026-03-13 10:28:27 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 10:28:27 -05:00
Owner
Copy Link

Originally created by @etiennecl on GitHub (Feb 28, 2026).

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

We are currently looking to migrate to better-auth to handle our auth and identities. The SDK is exactly what we are looking for in terms of flexibility and composability via plugins. We currently have an identity management component for login/registration. We also have an OpenID Provider & OAuth Provider attached to our identity provider.

We are leveraging our OP for 1P apps. We leverage the access token to access our API's and therefore when a user logouts from the App we want to also invalidate it's access to our API's without having to wait for the token to expire. To do that we leverage Back-Channel logout in order to invalidate access tokens bound to a specific session (sid).

Describe the solution you'd like

I would like the new OAuth Provider to support back channel logout. Each Oauth clients should have back_channel_uris: string[] property in it's schema so that when a session is invalidated better-auth send a POST request to all back_channel_uris configured as per the specification.

Describe alternatives you've considered

We are currently using Ory which support the back channel logout or could use Keycloak or Auth0.

Additional context

No response

Originally created by @etiennecl on GitHub (Feb 28, 2026). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. We are currently looking to migrate to better-auth to handle our auth and identities. The SDK is exactly what we are looking for in terms of flexibility and composability via plugins. We currently have an identity management component for login/registration. We also have an OpenID Provider & OAuth Provider attached to our identity provider. We are leveraging our OP for 1P apps. We leverage the access token to access our API's and therefore when a user logouts from the App we want to also invalidate it's access to our API's without having to wait for the token to expire. To do that we leverage Back-Channel logout in order to invalidate access tokens bound to a specific session (sid). ### Describe the solution you'd like I would like the new OAuth Provider to support back channel logout. Each Oauth clients should have `back_channel_uris: string[]` property in it's schema so that when a session is invalidated better-auth send a POST request to all back_channel_uris configured as per the [specification](https://openid.net/specs/openid-connect-backchannel-1_0.html#Backchannel). ### Describe alternatives you've considered We are currently using Ory which support the back channel logout or could use Keycloak or Auth0. ### Additional context _No response_
GiteaMirror added the enhancement label 2026-03-13 10:28:27 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#2936
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?