日韩性视频-久久久蜜桃-www中文字幕-在线中文字幕av-亚洲欧美一区二区三区四区-撸久久-香蕉视频一区-久久无码精品丰满人妻-国产高潮av-激情福利社-日韩av网址大全-国产精品久久999-日本五十路在线-性欧美在线-久久99精品波多结衣一区-男女午夜免费视频-黑人极品ⅴideos精品欧美棵-人人妻人人澡人人爽精品欧美一区-日韩一区在线看-欧美a级在线免费观看

歡迎訪問(wèn) 生活随笔!

生活随笔

當(dāng)前位置: 首頁(yè) > 编程资源 > 编程问答 >内容正文

编程问答

WIF - claims-based identity

發(fā)布時(shí)間:2024/4/17 编程问答 49 豆豆
生活随笔 收集整理的這篇文章主要介紹了 WIF - claims-based identity 小編覺(jué)得挺不錯(cuò)的,現(xiàn)在分享給大家,幫大家做個(gè)參考.

最近使用了Sharepoint 2010的開(kāi)發(fā),其中包括一個(gè)新的服務(wù)STS,看了一下,主要資料如下:

現(xiàn)有的認(rèn)證授權(quán)如Memebership的開(kāi)發(fā)支持已經(jīng)比較完善了,之所以引入WIF,主要是通過(guò)間接的形式抽象,使認(rèn)證和授權(quán)在分布式環(huán)境下更易使用。

With the inflationary growth of distributed systems and online businesses, in the last few years the increasing need for interoperable protocols that could tear down the walls between silos became clear. The big players in the IT industry got together and agreed on a set of common protocols that would support interoperable communications across different platforms. Some examples of those protocols are SOAP, WS-Security, WS-Trust, WS-Federation, Security Assertion Markup Language (SAML), and in more recent times, OpenID, OAuth, and other open protocols.Claims-based identity promotes separation of concerns at a level never achieved before in the identity management world.

Windows Identity Foundation (WIF) is Microsoft’s stack for claims-based identity programming. It is a new foundational technology which helps .NET developers to take advantage of the claims based approach for handing authentication, authorization, customization and in general any identity-related task without the need to write any low-level code.

?

經(jīng)典的claims-based identity過(guò)程

WIF的過(guò)程

?

identity providers (IP).

relying party (RP)

STS (Security Token Service).

WIF的具體過(guò)程:

1. WIF sits in front of your application in the ASP.NET pipeline. When an unauthenticated user requests a page, it redirects the browser to the identity provider pages.
2. Here the IP authenticates the user in whatever way it chooses (perhaps by showing a page with user name and password, using Kerberos, or in some other way). Then it manufactures a token with the required claims and sends it back.
3. The browser posts the token it got from the IP to the application, where WIF again intercepts the request.
4. If the token satisfies the requirements of the application (that is, it comes from the right IP, contains the right claims, and so on), the user is considered authenticated. WIF then drops a cookie, and a session is established.
5. The claims in the incoming token are made available to the application code, and the control is passed to the application.

?

參考資料

■ The WIF product home page on http://www.microsoft.com/wif

? WIF Runtime 和 WIF SDK
■? The Identity Developer Training Kit at http://go.microsoft.com/fwlink/?LinkId=148795

?? 很多的例子和概念展示
■ The WIF team blog at http://blogs.msdn.com/card

???? http://www.cloudidentity.net

■ The IdElement Show on Channel9: http://channel9.msdn.com/shows/Identity/

轉(zhuǎn)載于:https://www.cnblogs.com/2018/archive/2011/12/14/2284157.html

總結(jié)

以上是生活随笔為你收集整理的WIF - claims-based identity的全部?jī)?nèi)容,希望文章能夠幫你解決所遇到的問(wèn)題。

如果覺(jué)得生活随笔網(wǎng)站內(nèi)容還不錯(cuò),歡迎將生活随笔推薦給好友。