EapPeerQueryInteractiveUIInputFields function

The EapPeerQueryInteractiveUIInputFields function defines the implementation of an EAP method API that provides the input fields for interactive UI components to be raised on the supplicant.


DWORD WINAPI EapPeerQueryInteractiveUIInputFields(
  _In_          DWORD                   dwVersion,
  _In_          DWORD                   dwFlags,
  _In_          DWORD                   dwSizeofUIContextData,
  _In_    const BYTE                    *pUIContextData,
  _Out_         EAP_INTERACTIVE_UI_DATA *pEapInteractiveUIData,
  _Out_         EAP_ERROR               **ppEapError,
  _Inout_       LPVOID                  *pvReserved


dwVersion [in]

The version number of the API. Must be set to zero.

dwFlags [in]

A combination of EAP flags that describe the EAP authentication session behavior.

dwSizeofUIContextData [in]

The size of the context data in pUIContextData, in bytes.

pUIContextData [in]

A pointer to a BLOB that contains UI context data, represented as inner pointers to field data. The supplicant obtained these inner pointers from EAPHost run-time APIs.

pEapInteractiveUIData [out]

Pointer that receives an EAP_INTERACTIVE_UI_DATA structure that contains configuration information for interactive UI components raised on an EAP supplicant.

ppEapError [out]

A pointer to the address of an EAP_ERROR structure that contains any errors raised during the execution of this function call. After consuming the error data, this memory must be freed by passing a pointer to the error data to EapPeerFreeErrorMemory.

pvReserved [in, out]

Reserved for future usage. Must be set to NULL


EapPeerQueryInteractiveUIInputFields can be employed to support Single-Sign-On (SSO). The EAP_FLAG_PRE_LOGON flag in EapPeerBeginSession indicates to EAPHost that SSO should be provided. If the EapPeerResponseInvokeUI action code is received after calling EapPeerBeginSession, EAPHost then calls EapPeerQueryInteractiveUIInputFields, and later calls EapPeerQueryUIBlobFromInteractiveUIInputFields.

The supplicant should call always call the EapPeerQueryInteractiveUIInputFields function first after receiving the EapPeerResponseInvokeUI action code from EAPHost. If the EapPeerResponseInvokeUI action code isn't returned, or if EAP_E_EAPHOST_METHOD_OPERATION_NOT_SUPPORTED is returned, the supplicant should resort to the traditional model of invoking method interactive UI by calling EapPeerInvokeInteractiveUI. If there is an error, EapPeerQueryInteractiveUIInputFields will return a return code other than NULL.


Minimum supported client

Windows Vista [desktop apps only]

Minimum supported server

Windows Server 2008 [desktop apps only]



See also




Community Additions