Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This function indicates that one or more VerifyUsercalls are about to occur. An application call to VerifyUserwill result in multiple VerifyUser (LAP)calls, if the VU_UNTIL_SUCCESS flag is set. Before the LASS makes the first VerifyUser(LAP) call, it calls VerifyUserStart. The LAP can use this function to draw its UI. This is a LAP-exported function.

Syntax 

VOID VerifyUserStart(
  const GUID* 
AEKey,
  LPCWSTR 
pwszAEDisplayText,
  HWND 
hWndParent,
  DWORD 
dwOptions,
  PVOID 
pExtended
);

Parameters

AEKey

[in] Authentication event identifier. The identifier corresponds to the type of authentication required.

pwszAEDisplayText

[in] Pointer to the text for the LAP to display. This will be the same pwszAEDisplayText that is passed to LAPLockoutUserand VerifyUser (LAP)

hWndParent

[in] Handle to the parent window.

dwOptions

[in] A bitmask of options. The following table shows the possible values.

Value Description

VU_NO_UI

Return from VerifyUserStartwithout displaying the UI.

VU_HANDLE_MASTER_KEY

Handle master key encryption and decryption if master key encryption and decryption are supported.

VU_UNTIL_SUCCESS

Keep calling into the LAP until the user cancels, or until the user successfully verifies.
pExtended

Reserved. Must be zero.

Return Value

None.

Remarks

Note:
This function is called by the LASS, not the application. Therefore, no link library is exposed. .

Requirements

Header lap.h
Windows Embedded CE Windows CE 5.0 and later
Windows Mobile Pocket PC for Windows Mobile Version 5.0 and later, Smartphone for Windows Mobile Version 5.0 and later
Note This function is called by the LASS, not the application. Therefore, no link library is exposed. For more information see Creating a LAP.

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.