Can I interact with the user at all in my implementation of LsaApLogonUser? I'm implementing an authentication process, which involves a fairly complex interaction. This includes, for example: 1. Collect the username. 2a. Send a request to authentication server asking for a "challenge". 2b. Simultaneously, gather various user authentication info. 3. When 2a and 2b are done, unlock "challenge" response using user data. 4. Send "challenge" response back to authentication server to authenticate. I could do steps 2a and 2b in the GINA, but this just seems like the wrong place to do so. But with all the special UI routines in GINA to handle the possibility of a user interaction being interrupted, it sorta looks like user interaction in the authentication package is also wrong. Is there a decent place to draw that line? I don't want to perform steps 2a and 2b sequentially, because both could take a while. Thanks for any help, -- Chris Smith
