Understanding Claims-Based Authentication (CBA) Series
I wrote these posts ad-hoc because I have recieved this question more than anything else lately, likely due to the paradigm shift from legacy authentication technniques in SharePoint 2010. I tried to keep the language in localizable terminology in order to support the mult-lingual functions provided on the site as well. I broke it up into seperate posts as well to provide some level of categorization, some are big, some are small.
I know they might not be perfect, but it’s a beta-ish technology and writing 16 posts takes a fair amount of time. Along those lines, there might be some terminology interchanging going on because I was using the Geneva stack when I had started this. Just keep in mind that the following legend coordindates the Microsoft code names:
Active Directory Federation Services (ADFS) = Geneva Server
Windows Identity Foundation = Geneva Framework
Windows CardSpace = Windows CardSpace :)
- The Basics of the Identity Foundation
- Working With Identity in Applications
- Claims Based Identity
- Claims Creation
- How are Claims Used?
- What does ADFS v2 And Windows Identity Foundation do?
- The Relationship Between Claims Based Identity, Windows Identity Foundation, ADFS v2
- Claim Usage Within The Enterprise
- Claims Usage Between Enterprises
- Claims Usage On The Cloud (Internet)
- Delegating Claims
- Geneva Server – ADFS v2
- Self Issued Identity Providers
- Geneva Framework – Windows Identity Foundation
- Conclusion On Claims Authentication