Specifies that the Windows identity does not flow across asynchronous points, regardless of the flow settings for the execution context on the current thread.
The following sections describe attributes, child elements, and parent elements.
Specifies that the WindowsIdentity does not flow across asynchronous points, regardless of the ExecutionContext flow settings on the current thread.
|WindowsIdentity flows across asynchronous points depending upon the ExecutionContext flow settings for the current thread. This is the default.|
|WindowsIdentity does not flow across asynchronous points, regardless of the ExecutionContext flow settings on the current thread.|
|The root element in every configuration file used by the common language runtime and .NET Framework applications.|
|Contains information about assembly binding and garbage collection.|
In the .NET Framework versions 1.0 and 1.1, the WindowsIdentity does not flow across any user-defined asynchronous points. Starting with the .NET Framework version 2.0, there is an ExecutionContext object that contains information about the currently executing thread, and it flows across asynchronous points within an application domain. The WindowsIdentity is included in this execution context and therefore also flows across the asynchronous points, which means that if an impersonation context exists, it will flow as well.
Starting with the .NET Framework 2.0, you can use the
<legacyImpersonationPolicy> element to specify that WindowsIdentity does not flow across asynchronous points.
The common language runtime (CLR) is aware of impersonation operations performed using only managed code, not of impersonation performed outside of managed code, such as through platform invoke to unmanaged code or through direct calls to Win32 functions. Only managed WindowsIdentity objects can flow across asynchronous points, unless the
You can alter this default behavior in two other ways:
In managed code on a per-thread basis.
You can suppress the flow on a per-thread basis by modifying the ExecutionContext and SecurityContext settings by using the ExecutionContext.SuppressFlow, SecurityContext.SuppressFlowWindowsIdentity or SecurityContext.SuppressFlow method.
In the call to the unmanaged hosting interface to load the common language runtime (CLR).
If an unmanaged hosting interface (instead of a simple managed executable) is used to load the CLR, you can specify a special flag in the call to the CorBindToRuntimeEx Function function. To enable the compatibility mode for the entire process, set the
flagsparameter for CorBindToRuntimeEx Function to STARTUP_LEGACY_IMPERSONATION.
For more information, see the <alwaysFlowImpersonationPolicy> Element.
In a .NET Framework application, this element can be used only in the application configuration file.
For an ASP.NET application, the impersonation flow can be configured in the aspnet.config file found in the <Windows Folder>\Microsoft.NET\Framework\vx.x.xxxx directory.
ASP.NET by default disables the impersonation flow in the aspnet.config file by using the following configuration settings:
configuration> <runtime> <legacyImpersonationPolicy enabled="true"/> <alwaysFlowImpersonationPolicy enabled="false"/> </runtime> </configuration>
In ASP.NET, if you want to allow the flow of impersonation instead, you must explicitly use the following configuration settings:
<configuration> <runtime> <legacyImpersonationPolicy enabled="false"/> <alwaysFlowImpersonationPolicy enabled="true"/> </runtime> </configuration>
The following example shows how to specify the legacy behavior that does not flow the Windows identity across asynchronous points.
<configuration> <runtime> <legacyImpersonationPolicy enabled="true"/> </runtime> </configuration>