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
Upon successful logout, the SPA logout flow currently sends a 204 No Content response (reference). This differs from other flows (e.g., login), which return a 200 OK response with a JSON payload that includes instructions for further actions, most notably the redirect_browser_to action.
According to the documentation, post-logout redirect is already supported for server-rendered browser applications and the returnTo URL can already be specified in the Kratos config (default_browser_return_url) and when creating the logout flow (reference).
It would be nice to have it also for SPAs for consistent behaviour.
Describe your ideal solution
The logout flow for SPAs should return a 200 OK response with a JSON payload that allows the application to perform post-logout actions, such as redirecting the user to a specific URL.
Preflight checklist
Ory Network Project
No response
Describe your problem
Upon successful logout, the SPA logout flow currently sends a 204 No Content response (reference). This differs from other flows (e.g., login), which return a 200 OK response with a JSON payload that includes instructions for further actions, most notably the
redirect_browser_to
action.According to the documentation, post-logout redirect is already supported for server-rendered browser applications and the
returnTo
URL can already be specified in the Kratos config (default_browser_return_url
) and when creating the logout flow (reference).It would be nice to have it also for SPAs for consistent behaviour.
Describe your ideal solution
The logout flow for SPAs should return a 200 OK response with a JSON payload that allows the application to perform post-logout actions, such as redirecting the user to a specific URL.
Example
200 OK
Workarounds or alternatives
Currently I hard-code the post-logout redirect URL in the SPA.
Version
v1.3.1
Additional Context
No response
The text was updated successfully, but these errors were encountered: