{"id":1204,"date":"2013-10-11T16:28:09","date_gmt":"2013-10-11T16:28:09","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/webdev\/2013\/10\/11\/signalr-and-user-identity-authentication-and-authorization\/"},"modified":"2013-10-11T16:28:09","modified_gmt":"2013-10-11T16:28:09","slug":"signalr-and-user-identity-authentication-and-authorization","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/signalr-and-user-identity-authentication-and-authorization\/","title":{"rendered":"SignalR and user identity (authentication and authorization)"},"content":{"rendered":"

There are too many authentication types (Basic, Windows, Cookie, OAuth) to explain how to use all of them. In this sample, I focus on using Cookie Authentication to secure a website, a Persistent Connection, and a Hub. Authentication is configured on OWIN, you have to add some nuget packages and add code in Startup.cs. I started with a web project using the MVC Template. By default, it creates web forms to register users, input user credentials, configures an anti-forgery token for http requests, creates an entity framework repository for User Identity. For the self host server there is no template, so I created it using the previous project as sample but removed things like the anti-forgery token, MVC, and entity framework.<\/p>\n

The important thing to remember is OWIN takes care of authentication and all frameworks on top of OWIN (SignalR, MVC, WebApi, etc) simply consume the user identity provided by OWIN. So, if you can\u2019t see the identity on SignalR, the problem is in your OWIN configuration.<\/p>\n

A SignalR Persistent Connection<\/strong> gives you access to the user identity by overriding AuthorizeRequest method. The sample code below allows to create a persistent connection only to authenticated users. you could add more logic to allow only some user roles by using the method request.User.IsInRole(string role)   <\/p>\n\n\n\n
\n
namespace <\/span>Common.Connections\n{\n  <\/span>public class <\/span>AuthorizeEchoConnection <\/span>: <\/span>PersistentConnection\n  <\/span>{\n    <\/span>protected override bool <\/span>AuthorizeRequest(<\/span>IRequest <\/span>request)\n    {\n      <\/span>return <\/span>request.User != <\/span>null <\/span>&& request.User.Identity.IsAuthenticated;\n    }\n\n    ...\n\n  }\n}<\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
<\/p>\n
A SignalR Hub<\/strong> gives you access to the user identity using Context.User. If you want to restrict access to a Hub only to authenticated users, add the [Authorize] attribute. Do you want to allow only some user roles? Add [Authorize(Roles="myRole")]. Do you want to allow specific users? Add [Authorize(Users="myUser")]<\/p>\n\n\n\n
\n
namespace <\/span>Common.Hubs\n{\n  [<\/span>Authorize<\/span>]\n  <\/span>public class <\/span>AuthorizeEchoHub <\/span>: <\/span>Hub\n  <\/span>{\n    <\/span>public override <\/span>Task <\/span>OnConnected()\n    {\n      <\/span>return <\/span>Clients.Caller.hubReceived(<\/span>"Welcome " <\/span>+ Context.User.Identity.Name + <\/span>"!"<\/span>);\n    }\n\n    ...\n\n  }\n}<\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
<\/p>\n
Full sample code is here<\/a>. It contains a web host server and a self host server. Then you can use any of the clients to authenticate and establish a SignalR connection:<\/p>\n