You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I read quite a few federal logout discussions & issues in this repo on the topic that basically come down to creating a custom Next.js API endpoint that calls a hardcoded /endsession URL to kill the server session when calling next-auth signOut method that only kills the client session.
What I'm trying to wrap my head around is, is there a recommended way to utilize the OIDC .well-known data to call the value of the end_session_endpoint field instead of writing a custom endpoint and constructing a URL to and the server session?
Can it be a signOut config?
P.S. I saw that federated logout is smth that the next-auth team were looking to adopt. Would love to know if it's still the case
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I read quite a few federal logout discussions & issues in this repo on the topic that basically come down to creating a custom Next.js API endpoint that calls a hardcoded
/endsessionURL to kill the server session when calling next-authsignOutmethod that only kills the client session.What I'm trying to wrap my head around is, is there a recommended way to utilize the OIDC
.well-knowndata to call the value of theend_session_endpointfield instead of writing a custom endpoint and constructing a URL to and the server session?Can it be a
signOutconfig?P.S. I saw that federated logout is smth that the next-auth team were looking to adopt. Would love to know if it's still the case
Beta Was this translation helpful? Give feedback.
All reactions