Hello, What is the minimum I need to do to get Windows to call LsaApLogonUser in my custom authentication provider? I could work on making things work, but I can't even get Windows to call the function. I'm not trying to replace the login dialog or anything like that. Right now, I'd be thrilled with success at just beeping and then crashing the system every time someone tries to log in. At least it would be something different, and then I could figure out the rest. Thanks, Chris Smith
Hi, Each authentication package has its own specific message format used by LsaCallAuthenticationPackage. The MS default implementation of logon operations in W2K et XP ( in the dll msgina.dll) knows only the formats associated with the packages "MSV1_0" and "Kerberos". This is why msgina.dll use (in a hard coded way) only these authentication packages. If you want your authentication package to be called, you must implement your own gina dll that will call it explicitly. you can also create a stub gina dll that will rely on msgina.dll after doing some hooking on it that will redirect the Lsa API calls to your package thus tricking msgina. Cheers, -- Mounir IDRASSI IDRIX http://www.idrix.fr to reach : mounir_idrix_fr (replace the underscores with the at and dot characters respectively) "Chris Smith" wrote: > Hello, > > What is the minimum I need to do to get Windows to call LsaApLogonUser in > my custom authentication provider? I could work on making things work, > but I can't even get Windows to call the function. I'm not trying to > replace the login dialog or anything like that. Right now, I'd be > thrilled with success at just beeping and then crashing the system every > time someone tries to log in. At least it would be something different, > and then I could figure out the rest. > > Thanks, > > Chris Smith >
