See Also
 Important: |
|---|
| 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. |
The EAP framework is implemented in a dynamic-link library (DLL), eap.dll. Specific authentication extensions are implemented in separate DLLs. For example, the EAP-MD5 authentication extension is implemented in eapchap.dll. A single extension DLL may support more than one authentication extension type. For a particular extension to be used successfully, both the client and server must support it. Windows Embedded CE only supports EAP as a client.
Setup software must be provided to install and remove the DLL. The setup software should also create the appropriate keys and values for the authentication protocol in the system registry. The installation of each EAP DLL should create the following registry key:
HKEY_LOCAL_MACHINE\Comm\Eap\Extension\< EAP Type ID>
In the preceding path, < EAP Type ID> is the identifier of the authentication protocol. This identifier must be obtained from the Internet Assigned Numbers Authority (IANA). For example, EAP-MD5 is assigned the type number 4, and EAP-TLS is type number 13.
The setup software should remove this key when uninstalling the DLL.