Feature Description
Once the Session Manager removes the X-CSRF-TOKEN header requirement from the /sm/logout endpoint, the UI should simplify the logout implementation from the current fetch() with CSRF token header approach to a single browser redirect (window.location.href).
Proposed Solution
Once the Session Manager removes the X-CSRF-TOKEN header requirement from the /sm/logout endpoint, the UI should simplify the logout implementation from the current fetch() with CSRF token header approach to a single browser redirect (window.location.href).
Alternative Solutions
No response
Want to contribute?
Additional Context
No response
Feature Description
Once the Session Manager removes the
X-CSRF-TOKENheader requirement from the/sm/logoutendpoint, the UI should simplify the logout implementation from the currentfetch()with CSRF token header approach to a single browser redirect (window.location.href).Proposed Solution
Once the Session Manager removes the
X-CSRF-TOKENheader requirement from the/sm/logoutendpoint, the UI should simplify the logout implementation from the currentfetch()with CSRF token header approach to a single browser redirect (window.location.href).Alternative Solutions
No response
Want to contribute?
Additional Context
No response