Right... That clears it quite a lot for me. I guess I've just never done an app where separating these would make sense (e.g. never used Windows Integrated Authentication). For a typical username/password login I don't see too much use for separating these.
I was actually thinking that I might make a "User" object that implements both these interfaces to simplify for me (a web app)... Cheers, Miika On Dec 11, 2007 1:59 PM, Marc Brooks <[EMAIL PROTECTED]> wrote: > Simply put, IIdentity is WHO you are... IPrincipal is what you can > do... You can be identified as someone without having any particular > role in an application... think about a Intranet application where you > are automatically logged in via Windows Integrated Authentication. In > this case, you have an IIdentity calling our your login credentials. > However, unless you are recognized by that specific intranet > application, you may not have an IPrinicipal... > > Marc > > On Dec 11, 2007 12:28 AM, Miika Mäkinen <[EMAIL PROTECTED]> wrote: > > Hi all, > > I'm having hard time understanding what is the purpose of IPrincipal and > > IIdentity. Why are these 2 separate interfaces? To me it just > complicates > > matters... Does anybody know of a good article explaining... > > > > > > Cheers, > > Miika > > > > =================================== > > This list is hosted by DevelopMentor(R) http://www.develop.com > > > > View archives and manage your subscription(s) at > http://discuss.develop.com > > > > > > -- > "He uses statistics as a drunken man uses lamp-posts… for support > rather than illumination." Andrew Lang > > Marc C. Brooks > http://musingmarc.blogspot.com > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
