大网数据广告活动
网络与域名解析

Tunnel Method API Call Sequence

· 52CE 我爱测

Learn about the API call sequence for Tunnel Methods. See an overview and view additional available resources.

This topic covers the API call sequence for Tunnel Methods

Tunnel Method Call Sequence Overview

When Supplicant gets request for user identity and user data the following API call flow typically occurs.

  • The Supplicant calls EapHostPeerProcessReceivedPacket on EapHost, to process the packet received from the authenticator.
  • Upon processing this packet, EAPHost determines it as IdentityRequest packet and calls EapPeerGetIdentity on tunnel method to obtain the user identity to use for authentication.
  • If tunnel method needs to obtain user identity from the inner method, it calls EAPHostPeerGetIdentity on inner EAPHost, which in turn calls EapPeerGetIdentity on the inner method.

User Interaction with the Tunnel Methods API Call Flow

In certain cases, when the identity is not available, or when the user must provide additional information, Eap Method raises a user interface dialog box on the supplicant.

In such cases following call sequence typically takes place to get information directly from the user.

  • Tunnel Eap Method returns action code to invoke UI to EapHost. Supplicant calls EapHostPeerGetUIContextto obtain the current user interface context information for the user interface dialog box.

  • Supplicant then calls EapHostPeerInvokeInteractiveUI. This function uses the UI context information to raise an interactive user interface which is used to get credential information from the user. The UI process loads Eappcfg.dll and obtains the pointers to EapPeerInvokeInteractiveUI and EapPeerFreeMemory.

    [!Note]
    UI process typically collects UI or handles interactive UI and is separate from the supplicant process. Separating the two processes is not a requirement of EAPHost, but doing so has the advantage of allowing the UI process to interact with the desktop.

  • EapHost calls EapPeerInvokeIdentityUI on tunnel method to obtain user identity information.

  • In order to obtain user identity from inner method, tunnel method calls EapHostPeerInvokeIdentityUI on inner EAPHost.

  • Inner EAPHost calls EapPeerInvokeIdentityUI on inner method to invoke user identity UI.

  • EapHostPeerSetUIContext provides a new or updated UI context information to the EAP peer method loaded on EAPHost after the UI has been raised.

Following diagram explains the API Call Sequence for Tunnel Methods

tunnel methods api call sequence

Related topics

EAPHost Call Sequence

Supplicant API Call Sequence

EAPHost Supplicant API Reference

Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Win32 documentation
适用范围
Windows Win32 API · Source date 05/31/2018
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。