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
What is the bug?
When you login with a JWT using a request header or a query parameter, the token is stored in the authentication cookie.
Hence, there is a logout mechanism for JWT as sell. However, when you click the logout button, the resulting AJAX request returns a 404 because the logout route does not exist.
How can one reproduce the bug?
Steps to reproduce the behavior:
Login with a JWT.
Click Logout
Check the network requests for a 404
Nothing happens on the screen
What is the expected behavior?
The user should be logged out and depending on JWT config settings see a non authenticated state.
[Triage] Hi @jochen-kressin, thank you for filing this issue. This seems like a good change that would improve the state of things. We can mark this as triaged.
What is the bug?
When you login with a JWT using a request header or a query parameter, the token is stored in the authentication cookie.
Hence, there is a logout mechanism for JWT as sell. However, when you click the logout button, the resulting AJAX request returns a 404 because the logout route does not exist.
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
The user should be logged out and depending on JWT config settings see a non authenticated state.
What is your host/environment?
Do you have any additional context?
I believe this is just a faulty route path definition in JWT's routes: https://github.com/opensearch-project/security-dashboards-plugin/blob/main/server/auth/types/jwt/routes.ts#L29
That path does not correspond to the url used by the logout component.
The text was updated successfully, but these errors were encountered: