Skip to content
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

the doc should specify which auth methods support TCP and Websocket connections #321

Open
dberardo-com opened this issue Mar 13, 2024 · 1 comment

Comments

@dberardo-com
Copy link

should be clear whether a specific authentication strategy is meant for TCP-only or WS-only connections or goes well for both.

example: JWT --> only in WS ? or also TCP ?

@iegomez
Copy link
Owner

iegomez commented Mar 16, 2024

Hey, @dberardo-com!

I think you're confused, that's not a concern of the plugin. It doesn't matter what the protocol is. In fact, the websocket protocol relies on TCP connection and the plugin won't know about it.

The example shown in the docs I took from something I did years ago at work, but it really doesn't matter if you sending a plain http request or you're establishing a two way ws connection, it's all irrelevant to the plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants