We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Unauthorised access issues while accepting connection over websocket
Steps to reproduce the issue Run server and client on crypto-websockets
Error:
⚡ Running authentication on server websocket. token bearer arb-tokenValue userpass { username: 'alec', password: 'oviecodes' } x 401 Unauthorized at WebSocketsAdapter.done (file:///workspaces/glee/dist/adapters/ws/server.js:151:29)
On client side:
GETING ERROR x Unexpected server response: 401 at ClientRequest.<anonymous> (/workspaces/glee/node_modules/ws/lib/websocket.js:783:7)
The text was updated successfully, but these errors were encountered:
Hey @oviecodes LMK if I have missed sth.
Edit: I guess done(true), this fixes it but for any user and pwd
done(true)
Sorry, something went wrong.
Are you good on this @afzal442 ,
You're meant to write your authentication logic before calling done(true) or done(false), depending on the results of your logic.
done(false)
You're meant to write your authentication logic
I am afraid, wdym?
🎉 This issue has been resolved in version 0.26.10 🎉
The release is available on:
Your semantic-release bot 📦🚀
Successfully merging a pull request may close this issue.
Describe the bug
Unauthorised access issues while accepting connection over websocket
How to Reproduce
Steps to reproduce the issue
Run server and client on crypto-websockets
Error:
On client side:
The text was updated successfully, but these errors were encountered: