SignalR supplying authorization token -
I am struggling to decide how best to add authentication and authorization in my signal R service.
Currently it is hosted with a WebAP 2 web service in Owen, I use the OAuth2 carrier token to authenticate with those people, and it works perfectly though, me Wondering whether they are suitable for SignalR?
My client is Javascript-based, and if the signal is available then the indicator uses WebSockets. This means that I can not use the authorization header. I came to know that before connecting, I can supply tokens using but an OAuth2 access token will surely expire (and in my implementation relatively soon). I think that updating the qs property will not make a difference once specifically connected (especially with web sockets).
I think my question is, what is the best way to supply a safety token, ticket, or any type of authority information for Signal R? Preferably there is a method that can be compatible with my WebAP and Signal R, but I want to know that I am want doing this.
Thanks
It's happening sometime - but we give this signal For the Signal R request, auth used to search the cookie that only one sign-in user can subscribe to signaller notifications.
It does not control the case where the tokens have expired - since the cookie was checked only on the connector, it was not a problem for us.
Comments
Post a Comment