Geek Answers Handbook

ASP.NET Authentication: Why Custom Properties and Claims?

I really got lost in trying to understand ASP.NET Identity 2.1.0 right now, and you need to go back to the basics to better understand how cookies and claims work.

The main question is that I do not understand why I understand why the user needs properties, as well as claims: this is not a requirement only for the key + value +, and therefore it could be used to store properties (key + value )? * What is the advantage of saving two sets of properties (except for Typed get / sets in properties)? Is someone more transient than another? * Is it just to distinguish between what is serialized and rounded in the cookie (only claims, right?)? * Speaking of this ... just checking: are all claims that are rounded off being serialized in a cookie, or is it just a subset of them (e.g. ClaimTypes.Roles)?

Thanks for the help!

+4
source share
1

cookie. ApplicationUser . , ( ).

2 : ClaimsPrincipal : IPrincipal, HTTP- ( ). ClaimsPrincipal ApplicationUser, cookie.

ApplicationUser - , - . , cookie, , .

ApplicationUser. , . , . ApplicationUser, , - . , , , .

: cookie. cookie - , .

+4

More articles:


All Articles