[This is preliminary documentation and subject to change.]
The vendor that implements the authentication protocol may also provide a configuration user interface (UI) for the protocol. The configuration UI may be implemented in the same DLL as the authentication protocol, or in a separate DLL. Also, the DLL that implements the configuration UI may support more than one authentication protocol. The path to the DLL for the configuration user interface is stored in a registry value under the key for the authentication protocol. For more information about creating this registry value, see EAP Installation.
The DLL for the configuration user interface should export entry points for the following functions:
When the user creates a phonebook entry for a particular RAS server in the Dial-Up Networking UI, the user is able to select the authentication protocol that RAS should use. If the authentication protocol is configurable, the Dial-Up Networking UI calls RasEapInvokeConfigUI to invoke the configuration UI. The Dial-Up Networking UI stores the connection-specific configuration information returned by RasEapInvokeConfigUI in the phonebook entry. Additionally, the Dial-Up Networking UI stores the user-specific configuration information in the registry under HKEY_CURRENT_USER.
When RAS calls the RasEapBegin function for the authentication protocol, it will pass a PPP_EAP_INPUT structure that contains a pointer to the configuration information. After RasEapBegin returns, RAS will call RasEapFreeConfigUIData to free the memory occupied by the configuration information. Therefore, the authentication protocol should copy the configuration information into a private memory buffer during the call to RasEapBegin.
The vendor may add registry values under their registry key that specify default configuration information, and whether the user is required to enter configuration information when they create a phonebook entry. For more information, see EAP Installation.