|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.|
This function performs the user verification. It has basically the same parameters as the application-called VerifyUserfunction. This is a LAP-exported function.
BOOL VerifyUser( const GUID* AEKey, LPCWSTR pwszAEDisplayText, HWND hWndParent, DWORD dwOptions, PVOID pExtended );
[in] Pointer to the authentication event identifier. The identifier corresponds to the type of authentication required.
[in] Pointer to the text for the LAP to display. This will be the same psszAEDisplayTextas passed to LAPLockoutUser.
[in] Handle to the parent window.
[in] A bitmask of options. The following table shows the possible values.
When this flag is set, LAP cannot display UI or block on calls to VerifyUser. When using this value, the function will return TRUEonly if the user can be verified without displaying the UI. Otherwise, it will return FALSE.
When this flag is set, it indicates to handle master key encryption and decryption if master key encryption and decryption are supported.
When this flag is set, the LAP VerifyUserentry-point function will be called until the user cancels or until the call succeeds.
Notice that there may be multiple calls to VerifyUserduring the time between the call to VerifyUserStartand the call to VerifyUserStop. This enables you to cache state during the time between the call to VerifyUserStartand the call to VerifyUserStop.
Reserved. Must be set to NULL.
Returns TRUEif the user is verified, and FALSEotherwise. To provide more details about why the function failed, use SetLastError.
When an application calls VerifyUserwith the VU_UNTIL_SUCCESS flag set, the call can result in several calls into the LAP. To prevent UI flash, the LASS will call VerifyUserStartbefore any VerifyUser(LAP) calls are made. After all VerifyUsercalls have been made, the LASS will call VerifyUserStop.
When the application calls VerifyUser, the LAP displays its verification dialog. It is possible for a second application to run and display its UI on top of the LAP verification UI in the z order. If the second application then calls VerifyUser, it will block. To prevent this UI blockage, the LASS will call VerifyUserToTopto request the LAP to bring its UI to the top of the z order.
|This function is called by the LASS, not the application. Therefore, no link library is exposed.|
|The PromptForPasswdfunction is deprecated. Use the VerifyUserfunction instead.|
|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.|