-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebSocket Auth #505
Comments
Hello. The WS authentication is tricky and therefore is not implemented (yet). One solution would be to take the password from the connector configuration. The drawback would be that you could specify only one username-password per connection, and that it would be separated from the standard server users. |
Thank you for the prompt reply. |
I just implemented something (without testing). Please give it a try and let me know if it doesn't work. |
Many thanks for that enhancement. |
Cool. Thanks for testing it. |
Hi @gotthardp ,
As I understood there is no authentification for WebSocket connectors, is it true?
Could you please suggest – do you have in plans implementation of Basic Auth for WebSocket?
The text was updated successfully, but these errors were encountered: