EAP Peer Method API & Windows 8 issue

Question

We're using EAP Peer Method API in our project. Everything
works fine on Vista and Windows 7 but Windows 8 is giving us some troubles.
Our project uses native Windows WLAN API to start connection to 802.1x protected WiFi AP. For authentication we're using our implementation of EAP method (registered using regsvr32).
Regardless of OS, setting (proper) user credentials before starting connection will result in successful connection. Problem happens when user credentials are either not set or are wrong (like wrong password).
On Vista/Win7, you'd get a popup balloon, like on picture below, and clicking it would make EAP Host call one of functions in our EAP dll, allowing us to display dialog asking user for credentials. But on Win8, there is no popup balloon and our function doesn't
get called. That locks us out of certain usage scenarios we've supported thus far.
Function that I mentioned is 'EapPeerInvokeIdentityUI'
and it is being called on Vista/Win7.
If you need more detailed info, I'll list function
our EAP dll exports:
   DllRegisterServer
   DllUnregisterServer
   EapPeerFreeErrorMemory
   EapPeerGetInfo
   EapPeerInvokeConfigUI
   EapPeerConfigXml2Blob
   EapPeerCredentialsXml2Blob
   EapPeerConfigBlob2Xml
   EapPeerInvokeInteractiveUI
   EapPeerInvokeIdentityUI
   EapPeerFreeMemory
   EapPeerQueryCredentialInputFields
   EapPeerQueryUserBlobFromCredentialInputFields
   EapPeerQueryInteractiveUIInputFields
   EapPeerQueryUIBlobFromInteractiveUIInputFields
We've been doing some research and noticed that Win8's native EAP methods do show dialog to user when password is wrong, therefore we looked into related dll's exported functions and found one that seem interesting - 'EapPeerGetIdentityPageGuid'. We didn't
find any documentation on that function though, not even function signature, so we couldn't do much with it but we suspect it might be called instead of 'EapPeerInvokeIdentityUI' on Windows 8. If we guessed right, some information about 'EapPeerGetIdentityPageGuid'
and related functions would be great, otherwise any help about new Windows 8 behavior would be appreciated. 

Answer 1

Hi Ethann,
Just a reminder for the above query.
Looks like this is the limitation in Windows 8 where the 802.1x security prompts are integrated into network pane. Here is the link which gives a brief info on changes from win 7 to 8.
http://www.windowsnetworking.com/articles-tutorials/wireless-networking/wireless-changes-windows-81-and-server-2012-r2.html
We are planning to implement a minimal supplicant which takes care of 802.1x authentication. So that we have full  control on authentication. Is this
the only possible way?
Hope you have resolved this issue. Your help will reduce our dev effort. Please guide me to troubleshoot this issue. 
Thanks