Setting the Security on IWbemServices and Other Proxies
While in C++ you can set the security on the entire process by calling CoInitializeSecurity before connecting to WMI through IWbemLocator::ConnectServer. You can also change the authentication level, impersonation level, or the authentication service in a call that obtains a pointer to a WMI proxy, such as IWbemServices or IWbemCallResult. Calling CoSetProxyBlanket also allows you to change the authentication service (Kerberos, NTLM, or negotiate).
Scripts and Visual Basic applications only set security on proxies indirectly through calls to SWbemServices and other automation objects. For more information about setting and changing authentication and impersonation in script, see Setting the Default Process Security Level Using VBScript.
Changing security levels or services is primarily a concern when connecting to WMI on a remote computer that is running a different operating system. For more information, see Connecting Between Different Operating Systems.
A client application connects to a WMI proxy using an identity. An identity is a data object that consists of a user name, password, and authority settings. For a WMI client application, the call to the IWbemLocator::ConnectServer interface creates the initial identity. The ConnectServer method takes the identity in a set of three parameters, which you can set to NULL to indicate the current user. You can also specify a non-NULL parameter to indicate a specific user and domain. If the call is successful, ConnectServer returns a pointer through which you can access a variety of remote processes, such as a WMI service or the Windows operating system directly.
Like many COM interfaces, ConnectServer returns a pointer to a proxy. A proxy is a data object that represents a remote process, such as WMI or a remote provider. COM uses a proxy to allow developers access to remote data as though the data were local.
The following WMI interfaces use proxies:
- IWbemServices (SWbemServices scripting object)
The WMI Refresher is a special case because it is passed an IWbemServices pointer, whose security settings must be properly set. For more information about using refresher objects, see Accessing Performance Data in C++.
After you receive a pointer to a remote process, you can do one of two things. If you know what the process does, you can choose to set the security on the pointer and access the process normally. This is the case with most pointers to a WMI service. For more information, see Setting the Security Levels on a WMI Connection. Alternately, you need to access a different COM interface on the proxy, such as IUnknown::Release, through a call to the IUnknown interface on the proxy.
The distributed version of the Component Object Model (DCOM) negotiates the default authentication service (Kerberos, NTLM, or Negotiate), and you cannot specify the default authentication service using CoInitializeSecurity. Specifying RPC_C_AUTHN_DEFAULT in the authentication service parameter of CoSetProxyBlanket allows DCOM to select the appropriate service. For remote connections the default service is Negotiate, which is the recommended service for applications functioning in both Kerberos and non-Kerberos domains. For local connections, the default authentication service is NT LAN Manager (NTLM).
The following code example shows the default authentication service being used.
// The pWbemServices variable is of type IWbemServices* HRESULT hr = CoSetProxyBlanket( pWbemServices, //Proxy RPC_C_AUTHN_DEFAULT, //Authentication service RPC_C_AUTHZ_DEFAULT, //Authorization service COLE_DEFAULT_PRINCIPAL, //Server principal name used // by authentication service RPC_C_AUTHN_LEVEL_DEFAULT, //Authentication level RPC_C_IMP_LEVEL_IMPERSONATE, //Impersonation level COLE_DEFAULT_AUTHINFO, //Client identity EOAC_DEFAULT //Capability flags );
The code example in this topic requires the following reference and #include statements.
#define _WIN32_DCOM #include <wbemidl.h> #include <comdef.h> #pragma comment(lib, "wbemuuid.lib")
For scripting, it is recommended that you use the defaults that DCOM selects for remote calls. On the local machine you cannot specify an authentication service for calls to WMI. For more information, see Setting the Authentication Service Using VBScript and Constructing a Moniker String.