Question: Authentication over Websocket about server HOT 6 CLOSED

Currently this is not supported but with should be doable with the 3.0 version

from server.

You could probably do it with a middleware if you add the token as query string to the connection request. That seems to be the way SignalR solved the authentication problem.

from server.

This was a big issue on our side too.
To help to overcome this, I have hacked a lot into the code, and I do hate the way it is right now, but it is working fine. I think there are much better ways to do it, but if you'd like to see a solution, I can put a fork online with my hacks in it.

from server.

3.0 will allow setting message listeners. You should be able to check the payload and close the reader if it doesn't contain what you want. You can also send a reply to the client.

from server.

• Inherit from https://github.com/graphql-dotnet/server/blob/master/src/Transports.Subscriptions.Abstractions/IOperationMessageListener.cs
• Apply your authorization
• Write your reply using the writer or just complete the reader which should close the connection

from server.

Closing this. Please feel free to reopen if you have any questions.

from server.