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  :)

1. The Basics of the Identity Foundation
2. Working With Identity in Applications
3. Claims Based Identity
4. Claims Creation
5. How are Claims Used?
6. What does ADFS v2 And Windows Identity Foundation do?
7. The Relationship Between Claims Based Identity, Windows Identity Foundation, ADFS v2
8. Claim Usage Within The Enterprise
9. Claims Usage Between Enterprises
10. Claims Usage On The Cloud (Internet)
11. Delegating Claims
12. Geneva Server – ADFS v2
13. CardSpace
14. Self Issued Identity Providers
15. Geneva Framework – Windows Identity Foundation
16. Conclusion On Claims Authentication