Custom Credential Provider + 802.1x authentication

%3CLINGO-SUB%20id%3D%22lingo-sub-2392515%22%20slang%3D%22en-US%22%3ECustom%20Credential%20Provider%20%2B%20802.1x%20authentication%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2392515%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3BWe%20are%20developing%20a%20custom%20Credential%20Provider%20and%20want%20to%20emulate%20the%20single-sign-on%20behaviour%20of%20default%20Windows%20Credential%20Providers.%20OneX%20Credential%20Provider%20uses%20undocumented%20WLan*%20and%20Dot3*%20APIs%20to%20provide%20this%20functionality%20(invoked%20from%20IConnectableCredentialProviderCredential%3A%3AConnect()%20method).What%20is%20the%20best%20approach%20to%20enabling%20network%20connectivity%20on%20network%20adapters%20with%20802.1x%20authentication%20enabled%20using%20credentials%20collected%20with%20our%20custom%20Credential%20Provider%20(ie.%20implementation%20of%20our%20Connect()%20method)%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

 We are developing a custom Credential Provider and want to emulate the single-sign-on behaviour of default Windows Credential Providers. OneX Credential Provider uses undocumented WLan* and Dot3* APIs to provide this functionality (invoked from IConnectableCredentialProviderCredential::Connect() method).What is the best approach to enabling network connectivity on network adapters with 802.1x authentication enabled using credentials collected with our custom Credential Provider (ie. implementation of our Connect() method)?

0 Replies