Michael (a reader) recently wrote:
“You posted on your blog that System.IdentityModel is not tied to WCF…I understand how the claims, rights, and resources work. And I have created an Authorization Policy that implements IAuthorizationPolicy. But how do I make it all work together?”
I spent the last couple of months building some applications that use the classes found in System.IdentityModel for identity and access control. And I really like this model.
As with most of the other features introduced in .NET 3.0, the API is meant as a foundation (compare to WCF) and is a little raw. So while writing my code I also built a companion library boldly called LeastPrivilege.IdentityModel that adds functionality that makes it easier to build claims/identity based applications.
In the next couple of posts I will do a walkthrough of System.IdentityModel, how to use the classes found there (together), how they are used in WCF, how to use them outside of WCF and what my library adds to it.
If you have any specific questions – just post them here and I can try to incorporate them. Have fun.