Extensible Authentication Protocol (Compact 7)
3/12/2014
The Extensible Authentication Protocol (EAP) implementation allows third-party authentication code to interact with the implementation of the Point-to-Point Protocol (PPP) included in the Windows Embedded Compact-based Remote Access Service (RAS). EAP is also used with 802.1x and EAP over LAN (EAPOL) authentication.
With EAP, you can add a wide variety of authentication extensions to your OS, and provide a standard support mechanism for authentication schemes such as token cards, public-key, and s-key. EAP is a critical technology for virtual private networks (VPNs) that provide industry-standard security levels. EAP helps to protect VPNs against attacks by unauthorized users, and password guessing.
Windows Embedded Compact supports EAP as a client only.
Windows Embedded Compact supports the following authentication protocols:
- Extensible Authentication Protocol (EAP) Transport Level Security (TLS)
- Challenge-Handshake Authentication Protocol (CHAP)
- Protected Extensible Authentication Protocol (PEAP)
- Microsoft Challenge-Handshake Authentication Protocol 2.0 (MS CHAP V2)
To add this feature to your OS, see Extensible Authentication Protocol Catalog Items and Sysgen Variables.
For reference information, see the following:
In addition to the legacy support provided in the reference listed above, Windows Embedded Compact supports Native EAP methods. See the EAPHost Peer Method Reference for more information.