The implementation does not appear to populate the Context within a SignalR hub. I suspect this has something to do with SignalR passing the token back through the access_token query parameter and not the Authorization header. I updated the JwtMiddleware class to check for the query when the token is null from the Authorization header. This does successfully retrieve the correct Account and add it to the context Items within the JwtMiddleware, however that information is still not available anywhere within the SignalR Context object.

I will continue to try to bridge this gap and commit a fix if desired if I figure this out, any pointers are very welcome though.

I setup the project in local. But I am disappointed by the performances. How it is possible to take this time to handle a login? About 700ms in good case. I have a similar project in VertX (Java) and it takes 80ms for a similar things.