802.1x PLAP Credential Provider always returns E_FAIL from Connect() call, even when it succeeds. Is there a rationale for this?

Question

I have noticed that the in-box 802.1x PLAP/SSO Credential Providers that support WLAN and DOT3 SSO always return E_FAIL from the IConnectableCredentialProviderCredential::Connect() call even when the network connection/authorization succeeds.   Blissfully AuthIU appears to simply not care.

Is there a rationale for this pair of compensating behaviors?   I can understand that AuthUI simply logs the 'failure' and marches on but I don't understand what is being conveyed from constant E_FAIL return value from the actuall Connect method.

Has anyone encountered this and uncovered an explanation?

Are all PLAP providers supposed to do this (return E_FAIL) or are they supposed to return a result that is indicative of whether or not the [a] connection was established?

Does returning E_FAIL suppress AuthUI from calling Disconnect in the event of some subsequent failure?

Does returing a success ensure that AuthUI will call Disconnect in the event of some subsequent failure?

-Dave Cattley

---

David R. Cattley