Syntax

HRESULT InitializeClientContextFromName(
  [in]            BSTR ClientName,
  [in, optional]  BSTR DomainName,
  [in, optional]  VARIANT varReserved,
  [out]           IAzClientContext **ppClientContext
);

Parameters

ClientName [in]

Name of the security principal.

DomainName [in, optional]

Domain name in which the user account resides. The default value is NULL.

varReserved [in, optional]

Reserved for future use. This parameter can be one of the following values:

• varReserved.vt == VT_ERROR and varReserved.scode == DISP_E_PARAMNOTFOUND
• varReserved.vt == VT_EMPTY
• varReserved.vt == VT_NULL
• varReserved.vt == VT_I4 and varReserved.lVal == 0
• varReserved.vt == VT_I2 and varReserved.iVal == 0

ppClientContext [out]

A pointer to a pointer to the returned IAzClientContext object.

Return Value

If the function succeeds, the function returns S_OK.

If the function fails, it returns an HRESULT value that indicates the error. For a list of common error codes, see Common HRESULT Values.

Remarks

If possible, call the InitializeClientContextFromToken function instead of InitializeClientContextFromName. InitializeClientContextFromName attempts to retrieve the information available in a logon token had the client actually logged on. An actual logon token provides more information, such as logon type and logon properties, and reflects the behavior of the authentication package used for the logon. The client context created by InitializeClientContextFromToken uses a logon token, and the resulting client context is more complete and accurate than a client context created by InitializeClientContextFromName.

The DomainName and ClientName parameters must combine to represent a SidTypeUser.

The supported name formats are the same as those supported by the LookupAccountName function.

Important  Applications should not assume that the calling context has permission to use this function. The AuthzInitializeContextFromSid function reads the tokenGroupsGlobalAndUniversal attribute of the SID specified in the call to determine the current user's group memberships. If the user's object is in Active Directory, the calling context must have read access to the tokenGroupsGlobalAndUniversal attribute on the user object. Read access to the tokenGroupsGlobalAndUniversal attribute is granted to the Pre-Windows 2000 Compatible Access group, but new domains contain an empty Pre-Windows 2000 Compatible Access group by default because the default setup selection is Permissions compatible with Windows 2000 and Windows Server 2003. Therefore, applications may not have access to the tokenGroupsGlobalAndUniversal attribute; in this case, the AuthzInitializeContextFromSid function fails with ACCESS_DENIED. Applications that use this function should correctly handle this error and provide supporting documentation. To simplify granting accounts permission to query a user's group information, add accounts that need the ability to look up group information to the Windows Authorization Access Group.

Applications calling this function should use the fully qualified domain name or user principal name (UPN). Otherwise, this method might fail across forests if the NetBIOS domain name is used and the two domains do not have a direct trust relationship.

Requirements

See Also

IAzApplication

Allowing Anonymous Access

Send comments about this topic to Microsoft

Build date: 9/11/2009