🚀 go-pugleaf

"Mike Collins" <mikec@kr8.co.uk> wrote in message
news:3f96448f$1@newsgroups.borland.com...

> What calls my WlxLoggedOutSAS method and when?

Winlogon itself after it determines which GINA it needs to work with.

> The reason that I ask is that WlxLoggedOutSAS appears to
> be called when a logon attempt is made.  However the actual
> login is being made by MSGINA.dll not myGINA.dll.

You missed the point of what a GINA is then.  The fact that MSGINA is
displaying a dialog window is irrelevent.  For this particular function,
WinLogon has detected that a SAS event occured while a user is logged out
(such as the user pressing CTRL-ALT-DEL to login), so it asks the registered
GINA to handle the event.  The GINA can do whatever it wants internally in
that regard, as long as it tells WinLogon the final result.  It could
display a dialog window.  It could perform an auto-login.  It can do
whatever it wants internally as is needed for the situation.  The whole
point of a GINA is that WinLogon itself is not handling the details
directly, it is delegating the responsibility to GINA instead.

> The user enters there username and password and clicks OK,
> all within MSGINA.dll.

Only if you are actually using MSGINA.  WinLogon knows that a user login is
needed at some point (amongst other things), so when that time eventually
comes, it asks the registered GINA to handle it.  If MSGINA is used, it
happens to displays a dialog and waits for the user input before calling
LogonUser().  However, that is not a requirement.

> What happens then?  I know that (or I think) MSGINA.dll
> calls LogonUser() to process the logon request, so how does
> my WlxLoggedOutSAS end up being call

Because WinLogon is working with *your* GINA directly, expecting *your* GINA
to do the necessary work internally when needed.  Any time that WinLogon
needs to do something in regards to validating user logins, handling various
system states, etc. it is going to go to *your* GINA directly, since only
one GINA can be loaded by WinLogon itself.  Ignore the fact that you are
specifically performing a pass-through to MSGINA in your code.  In fact, if
you stop daisy-chaining with MSGINA altogether, you will see that *your*
GINA is still being called anyway.  If you look at the example of
WlxLoggedOutSAS() at MSDN, you will see that the example is calling
LogonUser() directly, not using MSGINA at all.  So daisy-chaining is not a
requirement, it is optional, used when you don't want to do all of the work
yourself manually.

I don't know how else to get that point across to you.  If *your* GINA is
the registered GINA, then *your* GINA is going to get called for everything
that WinLogin needs to do GINA-related.  Whatever happens internally is your
own business.


Gambit