JWT Proxy do not redirect websocket requests if token/cookie is missing #12575
Labels
kind/bug
Outline of a bug - must adhere to the bug report template.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
severity/P2
Has a minor but important impact to the usage or development of the system.
Description
When some code tries to access a secure server using websocket connection but token/cookie is missing JWT proxy redirects it to http(s) page. Since websocket URL would not allow setting cookie on loader.js side we should just forbid such a case.
The text was updated successfully, but these errors were encountered: