Windows 10上的凭据提供程序接口（TCP 10041） [英] Credential Provider Interface on Windows 10 (TCP 10041)

问题描述

我们有一个桌面应用程序可以修改用户登录体验。这在Windows 8中工作正常，除了一些小错误，在Windows 10（9926）的最后一个预览中。但是，我刚刚将我的9926构建系统升级到10041，现在我的凭证
提供程序根本不起作用！更糟糕的是，登录框完全混乱，以便人们可以登录。 

We have a desktop application that modifies the user logon experience. This works fine in Windows 8 and also, barring a few minor bugs, in the last preview of Windows 10 (9926). However, I have just upgraded my 9926 build system to 10041 and now my credential provider does not work at all!  Worse, the logon box is completely messed up so that so one can logon on. 

有谁知道在封面？有一个文档描述了凭据提供程序接口在Windows 8中的工作方式.Windows 10有什么类似的东西吗？

Does anyone know what has changed under the covers? There is a document that describes how the credential provider interface works in Windows 8. Is there anything similar for Windows 10?

推荐答案

Weebo，

Weebo,

刚开始看这个。到目前为止我看到的差异是logonui.exe可能会要求一些似乎没有记录的COM接口。在我们的过滤器CP中，我们现在将它们传递到Microsoft Credential Provider进行处理，
按原样返回它们。

Just started looking at this. The differences that I have seen so far are that the logonui.exe can ask for some COM interfaces that don't appear to be documented. In our filter CP we now pass them onto the Microsoft Credential Provider for processing and return them as is.

我还必须实现ICredentialProviderCredentialWithFieldOptions。

I've also had to implement ICredentialProviderCredentialWithFieldOptions.

我现在正在工作，但我现在坚持的是，似乎有一个新的接口ICredentialProviderCredentialEvents3。它的继承兄弟似乎有一个额外的方法SetFieldBitmapBuffer。找不到任何文档。

I am working now, but the bit I am now stuck on is that there appears to be a new interface ICredentialProviderCredentialEvents3. It seems to have an extra method SetFieldBitmapBuffer over its inherited brothers. Can't find any doc on it.

BTW  HP也是。

BTW HP too.

这篇关于Windows 10上的凭据提供程序接口（TCP 10041）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！