70 likes | 205 Vues
This article clarifies the relationship between Access Control Service (ACS) and Windows Identity Foundation (WIF), highlighting that ACS is a cloud service part of the Windows Azure platform, while WIF operates as a .NET runtime. ACS simplifies protocol handling, supporting standards like WS-Federation, OpenID, and OAuth 2.0. The article also discusses WIF's capabilities in token parsing and customization. Key takeaways include the distinction between ACS and WIF, their functionalities, and how to start a free trial of Azure services.
E N D
Objectives • Clarify ACS and WIF relationship
Cloud Service vs. .Net Assembly • ACS is a Cloud Service • Part of Windows Azure Platform • WIF is a .Netruntime • Runs as part of your web application or service. • Free out of band download
ACS - Protocol Handling • ACS does heavy lifting for handling protocols • WS-Federation • WS-Trust • OpenID • OAuth 2.0, OAuth WRAP • Facebook Graph • ACS issues normalized tokens • SAML • SWT
WIF - Token Parsing, Tooling • Parses incoming tokens • Exposes convenient .Net API • Design Time tooling via FedUtil wizard tool • Extensibility points: • Configuration sections • Custom token handlers • Authorization • Role based and claims based
Key Takeaways • ACS is a cloud service • WIF is .Net runtime • Heavy lifting for handling protocols and tokens • Runtime and design time
Next Steps • Sign up for free trial at http://www.microsoft.com/windowsazure/free-trial/ • Learn more at http://go.microsoft.com/fwlink/?LinkID=212360