Re: WlanSetProfileEapXmlUserData Security Context Question

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


Then I'd asked the MS product support, or the
manufacturer of the wireless device (as they could provide
the actual EAP handler for their driver)

--PA


P Becker wrote:
Thanks to you M, and Pavel A. (Sorry, this is my first post for help and after two weeks of struggling with this I let my frustration turn into impoliteness.)

There is no user interaction with the service. There is a GUI app that is a front end to the user and communicates with a Windows Service to handle the things like WLAN calls.

The call is successful and returns ERROR_SUCCESS. I'm using WlanSetProfileEapXmlData to include credentials in the wlan profile so that it will prevent windows from offering it's pop-up and asking for credentials.

I'm capturing the WLAN events and the only difference between this and other AP connections is that I never get the "wlan_notification_msm_connected" and "wlan_notification_msm_connection_complete" messages.

What do you mean when you say that the EAP credential could somehow be context specific? This could be the case, but I don't see how it would be. The service creates a wlan profile, modifies it to include the EAP credentials, and then connects on it's own. In all other cases where the EAP credential isn't added to the profile, it works. Even when it is set to "Use windows logon" instead of adding the credentials it works. And this code works fine when it is run through a debug app that acts like the service.

"m" wrote:

Does the call fail? with what error?
or does the call block waiting for you to enter credentials into a dialog on a non-interactive session?

If you don't know, then fire up a debugger an find out! Much as we may want to help you, these are things we can't for you ;)

In general, code will never work as a service if it displays any UI besides a consol and can't possibly work if it requires direct user interaction.

Now, i have no idea what this function does, but based on its description in MSDN, its behaviour changed with XP SP2 and the EAP credential is somhow context (user?) specific
.