了解使用Windows Native WPF Client的ADFS登录 [英] Understanding ADFS Login With Windows Native WPF Client

问题描述

我已经阅读了很多有关与NodeJS / Angular或另一个前端Web框架进行ADFS集成的文献，以及一般流程的工作原理（并通过Auth0-Angular入门代码构建了概念证明），但是我不了解如何使用本机WPF Windows应用程序？

I've read through lots of the literature on ADFS integration with NodeJS/Angular or another front end web framework and how that general flow works (and built a proof of concept through Auth0 - Angular starter code), but I'm not understanding how this would work with a native WPF Windows application?

使用基于浏览器的客户端（和NodeJS后端），用户将被重定向到浏览器中的ADFS登录页面然后使用SAML进行身份验证。

With browser based clients (and NodeJS backend), the user is redirected to their ADFS login page in the browser and then is authenticated with SAML.

对于WPF客户端（和NodeJS后端），没有浏览器。此外，用户是否已经通过其Windows帐户进行身份验证？ WPF应用程序是否必须打开内部浏览器来进行身份验证（对我来说似乎有些讨厌）？还是有更简单的方法来做到这一点？其他企业本机Windows应用程序如何实现这种看上去不太明显的ADFS SSO？

With a WPF client (and NodeJS backend), there is no browser. Additionally, isn't the user already authenticated to their Windows account? Would the WPF application have to open up an internal browser to do this authentication (seems a little "jank" to me)? Or is there a easier way to do it? How do other enterprise native Windows applications achieve this seemless ADFS SSO?

推荐答案

对于本机，您使用ADAL库（使用OpenID）

For Native, you use the ADAL libraries (which use OpenID Connect).

不要使用SAML，因为这需要浏览器重定向，这在WPF中是很棘手的。

Don't use SAML as this requires browser redirects which as you have identified is tricky in WPF.

有一个很好的例子，但请注意，它使用的是ADFS 3.0。

There's a good example here but note this uses ADFS 3.0.

在ADFS 4.0中，所有这些都内置在向导中

In ADFS 4.0, this is all built into the wizard.

这篇关于了解使用Windows Native WPF Client的ADFS登录的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！