How do I support the CPUS_UNLOCK_WORKSTATION scenario? about windows-credentials-provider HOT 2 CLOSED

So I've switched gears a little bit here, and am going to wrap the Windows password provider.

I have so far successfully translated this sample https://github.com/pauldotknopf/WindowsSDK7-Samples/tree/master/security/credentialproviders/samplewrapexistingcredentialprovider to your C# code, but I am kind of confused on how I would wrap the ICredentialProviderCredential object.

In the C++ example, there is an initialize method that takes in a 'ICredentialProviderCredential', and then they assign it to their local object like so: _pWrappedCredential = pWrappedCredential.

I don't see an initialize method in your TestWindowsCredentialProviderTile.cs class, or even in the 'ICredentialProviderCredential' interface here https://docs.microsoft.com/en-us/windows/desktop/api/credentialprovider/nn-credentialprovider-icredentialprovidercredential.

How can I get a reference to the password provider's ICredentialProviderCredential and call it from my wrapped credential?

from windows-credentials-provider.

Hi @nadcraker,

IMHO you shouldn't wrap the default credential provider. Unless it's a fun project it could limit you from different OS customisations that you might have to do.

Right now I am pretty sure that the CPUS_UNLOCK_WORKSTATION scenario is not supported.
The problem is the method CredPackAuthenticationBuffer which creates a KERB_INTERACTIVE_UNLOCK_LOGON structure (internally) with MessageType always KerbInteractiveLogon.

The proper C++ implementation in pgina looks like this.

I hope that helps,
Alexander

from windows-credentials-provider.