IWbemUnsecuredApartment interface
The IWbemUnsecuredApartment interface allows client applications to determine whether Unsecapp.exe performs access checks on asynchronous callbacks. Unsecapp.exe supports both IUnsecuredApartment and IWbemUnsecuredApartment interfaces.
When to use
IWbemUnsecuredApartment should be used for asynchronous calls to Windows Management Instrumentation (WMI) from client applications running on Windows Server 2003. By setting the WBEM_UNSECAPP_FLAG_TYPE flag, an application can programmatically specify whether or not access control is performed by Unsecapp.exe.
Members
The IWbemUnsecuredApartment interface inherits from IUnsecuredApartment. IWbemUnsecuredApartment also has these types of members:
Methods
The IWbemUnsecuredApartment interface has these methods.
| Method | Description |
|---|---|
| CreateSinkStub |
The CreateSinkStub method is similar to the IUnsecuredApartment::CreateObjectStub method. It creates an object forwarder sink and performs access checks for receiving asynchronous calls from WMI. |
Remarks
IWbemUnsecuredApartment is similar to IUnsecuredApartment, which also creates a sink in a separate process. In Windows 2000 and Windows XP, you must perform your own access checks because Unsecapp.exe does not do access checking on those platforms. For more information, see Performing Access Checks.
HKEY_LOCAL_MACHINE\software\microsoft\wbem\CIMOM\UnsecAppAccessControlDefault
Requirements
|
Minimum supported client | None supported [desktop apps only] |
|---|---|
|
Minimum supported server | Windows Server 2003 [desktop apps only] |
|
Header |
|
|
Library |
|
|
DLL |
|
See also
- Setting Security on an Asynchronous Call
- IUnSecuredApartment
- Lowering the Security for a Sink in a Separate Process
- Performing Access Checks
Send comments about this topic to Microsoft
Build date: 11/19/2012
