However, there is no way to pass an Authorization header onto a websocket (as far as I understand). One alternative is to pass the full token in the query parameters, but this is not secure e.g. ws://example.com/ws?token=XXX
Hope that makes sense, and thank you for any help!
Unfortunately I’m not sure there is an easy workaround for this - Is it an option to pass the token as a custom header when initially setting up the websocket connection?