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

Transferring Data Between the Supplicant and EAP Methods

· 52CE 我爱测

Learn about transferring data between the Supplicant and EAP methods. Transferring data between methods is accomplished by using EAP attributes.

Using EAP attributes allows data to be exchanged between supplicants and EAP methods.

Attribute Consumption

EapHostPeerBeginSession consumes EAP attributes that are passed directly to the configured EAP method. Similarly, EAP methods are free to return an action code that indicates to the supplicant that attributes are available and that it should collect the attributes using EapHostPeerGetResponseAttributes.

For more information, see the following topics.

Supplicants are expected to ignore attributes that they do not recognize or cannot act upon. Using EapHostPeerSetResponseAttributes these ignored attributes are sent back to EAPHost and the EAP method.

Vendor Specific Attributes

By using the vendor-specific EAP attribute, EAP methods and supplicants can engage in data exchange for a specific purpose. Vendor-specific attributes are ignored by supplicants and methods that do not support the vendor-specific attribute.

For more information, see the following topics.

Related topics

Configuring the EAP Method User Interface

Enabling Group Policy

Implementing In-Band NAP Support for EAP Methods

Implementing NAP Support for EAP Methods

EAPHost Supplicants

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)

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

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