Provides authorization access checking for service operations.
Assembly: System.ServiceModel (in System.ServiceModel.dll)
Checks authorization for the given operation context.
Checks authorization for the given operation context when access to a message is required.
Checks authorization for the given operation context based on default policy evaluation.
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.)
Gets the set of policies that participate in policy evaluation.
Serves as the default hash function. (Inherited from Object.)
Returns a string that represents the current object.(Inherited from Object.)
This class is responsible for evaluating all policies (rules that define what a user is allowed to do), comparing the policies to claims made by a client, setting the resulting AuthorizationContext to the ServiceSecurityContext, and providing the authorization decision whether to allow or deny access for a given service operation for a caller.
The CheckAccessCore method is called by the Windows Communication Foundation (WCF) infrastructure each time an attempt to access a resource is made. The method returns true or false to allow or deny access, respectively.
This class does not perform any authorization and allows users to access all service operations. To provide more restrictive authorization, you must create a custom authorization manager that checks custom policies. To do this, inherit from this class and override the CheckAccessCore method. Specify the instance of the derived class through the ServiceAuthorizationManager property.
By getting the RequestContext property, which returns a RequestContext object, the application can access the entire request message (RequestMessage) and perform the authorization decision accordingly.
For an example, see How to: Create a Custom Authorization Manager for a Service.
For more information, seeCustom Authorization.
You can set the type of a custom authorization manager using the <serviceAuthorization> element in a client application configuration file.
Available since 3.0
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.