title: Implementing Authorization in a Self Hosted SignalR Server accessed from Web
body: <p>I'm looking for some guidance on how to implement authorization security for SignalR on a back end service running in a self-hosted (non-IIS) environment, that is called from a Web application. The backend app is basically a monitor that fires SignalR events back to the HTML based client. This all works fine (amazingly well actually).</p>
  
  <p>However, we need to restrict access to the server for authenticated users from the Web site. So basically if a user is authenticated on the Web site, we need to somehow pick up the crendentials (user name is enough) and validation state in the backend app to decide whether to allow the connection as to avoid unauthorized access.</p>
  
  <p>Can anybody point at some strategies or patterns on how to accomplish this sort of auth forwarding?</p>