claims-based-identity

What the claim of type http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier should be used for? This is the main question, and here are additional ones. How does it differ from http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name claim? Is it permanent for particular user as opposed to name claim? Is it globally-scoped or IdP-scoped? EBarr Name , is just that a name. If we're talking person, think "Eric"; a server "file01". A NameIdentifier is the ID for an object. Turning back to our person object, Eric's UserID might be 435 in your database. For the server the

I have an MVC app that I would like to add claims-based authorization to. In the near future we will use ADFS2 for federated identity but for now we will used forms auth locally. Has anyone seen a tutorial or blog post about the best way to use WIF without an external identity provider? I have seen the following but it is a year old now and I think there should be an easier solution: http://geekswithblogs.net/shahed/archive/2010/02/05/137795.aspx You can use WIF in MVC without an STS. I used the default MVC2 template, but it should work with MVC 3 too. You need to: 1- Plug WIF 's

Are there any decent examples of the following available: Looking through the WIF SDK , there are examples of using WIF in conjunction with ASP.NET using the WSFederationAuthenticationModule (FAM) to redirect to an ASP.NET site thin skin on top of a Security Token Service (STS) that user uses to authenticate (via supplying a username and password). If I understand WIF and claims-based access correctly, I would like my application to provide its own login screen where users provide their username and password and let this delegate to an STS for authentication, sending the login details to an

I am having an issue with the anti-forgery token :( I have created my own User class which worked fine but now I am getting an error whenever I go to the /Account/Register page. The error is: A claim of type ' http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier ' or ' http://schemas.microsoft.com/accesscontrolservice/2010/07/claims/identityprovider ' was not present on the provided ClaimsIdentity. To enable anti-forgery token support with claims-based authentication, please verify that the configured claims provider is providing both of these claims on the ClaimsIdentity

I am trying to create a user using claim identity asp.net I get this error while creating claims identity user. ApplicationUser user = new ApplicationUser { EmailConfirmed = true, UserName = model.myUser.Email, Email = model.myUser.Email , PhoneNumber = model.myUser.PhoneNumber, PhoneNumberConfirmed = true, UserImagePath = model.myUser.UserImagePath, FirstName= model.myUser.FirstName, LastName = model.myUser.LastName, DateOfBirth = model.myUser.DateOfBirth, Culture = model.myUser.Culture, Role = model.myUser.Role }; but when the code was var user= new ApplicationUser { UserName = model.myUser

Well, not exactly to a 5-year-old, but please avoid buzzword and enterprisespeak if possible. Claims-based authentication seems to be all the rage now, but I could not find a simple and down-to-earth explanation of what it actually is, how is it different from what we have now (I assume "what we have now" to be role-based authentication), what are the benefits of using it, etc. @Marnix has a pretty good answer, but to step away from the technical aspect of it: Claims Based Authentication is about defining who you trust to give you accurate information about identity, and only ever using that