Configures the location of a custom implementation of the authentication service.
Assembly: System.Web.Extensions (in System.Web.Extensions.dll)
Determines whether the specified object is equal to the current object.(Inherited from Object.)
Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.(Inherited from Object.)
Serves as the default hash function. (Inherited from Object.)
Returns a string that represents the current object.(Inherited from Object.)
The authentication Web service is used by AJAX-enabled applications to log on and log off from client script. You can useto provide the path of an alternative implementation of the authentication Web service instead of using the built-in Web service that is provided by the AJAX features of ASP.NET.
To use the authentication service in your application, you must enable it in the configuration file. If you use the built-in authentication Web service, you do not have to explicitly declare the authentication service manager on the page.
To create your own authentication service, you must implement a Web service that has two methods: Login and Logout. In addition, these methods require the same signature of the built-in authentication Web service.
The following example shows the basic class structure that must be implemented in a custom authentication Web service class.
To use a custom authentication Web service, you can add the service declaratively in markup by including an <AuthenticationService> element inside the <asp:ScriptManager> element on the page, as shown in the following example.
<asp:ScriptManager ID="SM1" runat="server"> <AuthenticationService Path="MyAuthenticationService.asmx" /> </asp:ScriptManager>
You can also programmatically configure Path to use a custom authentication Web service.
Available since 3.5
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.