Product Description
This ebook collects the two parts of SilverlightShow article series Authorization in Silverlight, together with source code.
From the author: As we know, Silverlight is very capable platform for building Line of Business applications today, both in and out of the browser. It’s come to the point that – at least in my experience – a lot of desktop applications are now built with Silverlight instead of WinForms, skipping over WPF completely.
With that in mind, it’s pretty weird that there’s an essential part that seems to be missing: authentication & authorization. When you look at the Silverlight Core CLR, there’s not much there concerning this – although it’s a no-brainer for business and enterprise applications: you need to make sure certain parts of your application are only available to users that are authenticated or have a specific role. Sure, you can use the hosting web page & ASP .NET authentication to ensure only authenticated persons can reach your Silverlight application, but there’s no out of the box way to enable or block a user from navigating to a specific view in your application.
Luckily, it only requires a little bit of coding and all in all: it’s quite easy to enable authenticated & authorized navigation in your Silverlight applications, mainly thanks to the introduction of a new class in Silverlight 4: the custom content loader.
In this ebook, we’ll look into enabling scenarios to enable/disable certain parts of your application for authenticated users, and to automatically ask the user for his credentials if he’s trying to access a part of the application that requires him to be authenticated or to have a specific role.
Table of Contents:
Chapter 1: Authorized navigation
Introduction
Introducing: the Custom Content Loader
The required parts
Uri right mappings: who can access which resource?
The Authentication context
Our own custom content loader
Bringing it all together…
Conclusion
Chapter 2: Manipulating the UI
Introduction
The not-so-cool yet oh-well-it-works way
Introducing a better approach: attachable properties.
The Authorization Service
Helper method: setting the target properties.
Using this in XAML
Conclusion
Buy from:
