GINA: token becomes invalid all of a sudden

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

In my gina.dll, after several logins and logouts, the token becomes invalid
all of a sudden between WlxLoggedOutSAS and WlxActivateUserShell.

The token is obtained from LogonUser called within WlxLoggedOutSAS.
ImpersonateLoggedOnUser is successful right before returning
WLX_SAS_ACTION_LOGON. However, when WlxActivateUserShell is called,
ImpersonateLoggedOnUser fails with the very same token. My current
implementation is to return FALSE in WlxActivateUserShell and ask the user to
login again.

There seems to be some strange things going on in WinLogon.exe between
calling WlxLoggedOutSAS and WlxActivateUserShell. Is there any way to find
out what WinLogon.exe does between the two calls?

.

Relevant Pages

  • Re: MSGINA with Novell
    ... As far as I can tell, the reason the WlxActivateUserShell from MSGina.dll ... If you use your own WlxLoggedOutSAS, ... CreateProcessAsUser, so Winlogon will die. ... your login scripts don't run, ...
    (microsoft.public.platformsdk.security)
  • Re: Replacement GINA using smart cards fail to display user Taskbar and user Icons.
    ... have put code in place to filter the WlxLoggedOutSAS to MSGINA.DLL and the ... > Taskbar is a main component of shell, and from your description, taskbar ... > WlxActivateUserShell, I could not find any problems inside it. ... > Microsoft Online Partner Support ...
    (microsoft.public.platformsdk.security)
  • Gina - WlxActivateUserShell is never called
    ... I am writing a custom Gina running on XP. ... In WlxLoggedOutSAS I return WLX_SAS_ACTION_LOGON ... But WlxActivateUserShell never gets called, instead WlxDisplaySASNotice gets ...
    (microsoft.public.platformsdk.security)