For example, you might authenticate your users with ASP.NET forms authentication, and then in your hub, enforce which users or roles are authorized to call a method. You authenticate users as you would normally in your application, and work with the results of the authentication in your SignalR code. Instead, you integrate the SignalR features into the existing authentication structure for an application. SignalR does not provide any features for authenticating users. Automatically generated JavaScript proxy files.Reconciling a change in user status with an active connection.Do not use groups as a security mechanism. How SignalR prevents Cross-Site Request Forgery This document contains the following sections: If you have questions that are not directly related to the tutorial, you can post them to the ASP.NET SignalR forum or. Please leave feedback on how you liked this tutorial and what we could improve in the comments at the bottom of the page. Software versions used in this topicįor information about earlier versions of SignalR, see SignalR Older Versions. This article describes the security issues you must consider when developing a SignalR application. This documentation isn't for the latest version of SignalR.
0 Comments
Leave a Reply. |