Exploring declarative identity

most enterprise applications Programs require some basic user security functions. They must at least authenticate their user identities, many of which also need to authorize access to specific features so that only privileged users can use them. Some applications must further review user usage. In Windows ^{, these functions are built into the operating system and are usually easily integrated into applications. With the integrated authentication feature of windows, you do not have to create your own authentication protocol or manage your database. You can use a few codes to implement identity authentication by using access control lists (ACLs), simulations, and groups. In fact, this recommendation applies no matter what operating system you use. Close integration with security features in the operating system is almost always a more ideal way than re-creating those features. But what if you want to extend the scope to users without a Windows account? What if the user doesn't need windows at all? More and more applications need to expand the scope, and this seems to be against common sense. This topic describes the new identity model in Microsoft . NET Framework 3.0. This model aims to help solve the preceding and other problems.}

MsdnArticle: Http://msdn.microsoft.com/msdnmag/issues/07/09/securitybriefs/Default.aspx? Loc = ZH
Microsoft switching Sharepoint to claims-based authentication:
Http://www.networkworld.com/news/2007/101607-microsoft-switching-sharepoint.html
Building a claims-based security model in WCF
Http://www.theserverside.net/tt/articles/showarticle.tss? Id = claimsbasedsecuritymodel

Authorization based on the WCF Service

Http://msdn.microsoft.com/zh-cn/magazine/cc948343.aspx