Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Lot of great information, thanks! App is actually Silverlight app with portion of server exposed as WCF RESTful service. Claims-Based looks interesting but I didn't notice concept of user and autorization inside of it. Interesting article I just found: geekswithblogs.net/shahed/archive/2010/02/05/137795.aspx Commented Jun 14, 2011 at 20:58
  • @katit: Virtually all authentication/authorization in .NET is based on the IPrincipal interface. If you're doing claims-based authorization then you use an IClaimsPrincipal for that, and cast the IPrincipal to IClaimsPrincipal when you want to do claim checks. You'll be writing a lot of your own code if you want to fit it in with (for example) Forms Authentication, but obviously it can be done (as per the link). Commented Jun 14, 2011 at 21:06
  • the question is.. Maybe it's easier to just add another "Group" level to membership/role providers or write own provider? Pretty much same amount of work as implementing Microsoft ones Commented Jun 14, 2011 at 21:17
  • 3
    @katit: Famous last words. Don't invent your own unless you have a very good reason to invent your own ("it seems easier" isn't a good reason; it only seems easier when you've had no direct experience and thus have no ability to judge the amount of work required). Commented Jun 14, 2011 at 21:40