Answering my own question by more digging:
A separate application is not required. Basically, you create a connection
object in the network control panel (New connection), then set its Properties
/ Security / Advanced, to use Extensible Authentication Procotol (EAP). When
you do this, if you have registered the EAP sample DLL on the system, it will
appear in the dropdown list of EAP options. Select it and save the
connection object.
Now selecting the connection object and choosing "Connect" will invoke the
DLL, and you will see a credentials dialog presented by the sample DLL prior
to the connection attempt with the remote server.
"Bugnut" wrote:
> The sample produces a sample common DLL that is to be installed on both
> client and server machines, providing an implementation of EAP type 20.
>
> Question: I'm hoping that this isn't just an abstract sample. Is there a
> testbed application or some other documentation that might explain how to see
> this sample DLL actually in action? Ultimately, I'm looking for information
> regarding deploying a custom authentication technology on Windows clients and
> a RADIUS backend server that will authenticate them. I can build the sample,
> and get it registered, but I'm missing the connecting dots about how it gets
> invoked. Any leads appreciated.
>
|