[This is preliminary documentation and subject to change.]
Microsoft® Windows NT®, vendors can implement EAPs, also known as authentication protocols, in Dynamic Link Libraries (DLLs). A DLL for the authentication protocol must reside on both the client and server computers. For simplicity, the client and server DLLs will often be identical; however, this is not a requirement. Also, note that the same DLL may support more than one authentication protocol.
The vendor should provide setup software to install and remove the DLL. The setup software should also create 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\System\CurrentControlSet\Services\Rasman\PPP\EAP\<eaptypeid>
In the preceding path, <eaptypeid> is the ID of the authentication protocol. The vendor must obtain this ID from the Internet Assigned Numbers Authority (IANA).
The setup software should remove this key when uninstalling the DLL. The system will remove this key if the user uninstalls RAS.