{"id":415,"date":"2009-03-17T04:08:00","date_gmt":"2009-03-17T13:08:00","guid":{"rendered":"http:\/\/www.cloudidentity.com\/blog\/2009\/03\/17\/a-visual-tour-of-the-net-access-control-service-part-2-fun-with-scopes-and-issuers\/"},"modified":"2009-03-17T04:08:00","modified_gmt":"2009-03-17T13:08:00","slug":"a-visual-tour-of-the-net-access-control-service-part-2-fun-with-scopes-and-issuers","status":"publish","type":"post","link":"https:\/\/www.cloudidentity.com\/blog\/2009\/03\/17\/a-visual-tour-of-the-net-access-control-service-part-2-fun-with-scopes-and-issuers\/","title":{"rendered":"A visual tour of the .NET Access Control service, part 2: fun with scopes and issuers"},"content":{"rendered":"
digg_url = “http:\/\/blogs.msdn.com\/vbertocci\/archive\/2009\/03\/17\/a-visual-tour-of-the-net-access-control-service-part-2-fun-with-scopes-and-issuers.aspx”;digg_title = “A visual tour of the .NET Access Control service, part 2: fun with scopes and issuers”;digg_bgcolor = “#FFFFFF”;digg_skin = “normal”;digg_url = undefined;digg_title = undefined;digg_bgcolor = undefined;digg_skin = undefined;<\/div>\n

Here we are again. I am just back from Belgium\u2019s TechDays<\/a>, and I can still savor the nice feeling you get from talking in front of a very interested audience \ud83d\ude42 I\u2019m really glad to see that both the cloud and claims based identity<\/a> are enjoying the attention they deserve! I have been asked to share the samples I have shown in my two sessions: sharing the end to end demo I have shown for Geneva will require some time & creativity, but I can certainly give more details about one of the ACS demo. In fact, that\u2019s the perfect excuse for writing the promised follow-up to the Visual Tour of the ACS<\/a> post.<\/p>\n

Recap<\/h1>\n

In the last installment<\/a> we took a good look at the structure of an ACS solution, by examining the Echo sample from the SDK with the Azure Services Management Console<\/a>. <\/p>\n

We briefly went through the steps of solution provisioning and solution credentials management; then we examined the list of STSes we get for every solution, focusing on the one dedicated to the ServiceBus. We listed the various elements we can use for defining our access logic: scopes, claim types, issuers, certificates\u2026 and above all, rules. We examined the default rules that are available in the default ServiceBus scope, and observed their behavior while running the Echo sample. It\u2019s now time to snap out of this look-don\u2019t-touch spell and mess with some settings!<\/p>\n

The \u201cVote for Hardware\u201d Scenario<\/h1>\n

Let\u2019s say that your business is leasing hardware to business customers and providing all-inclusive maintenance. For example: Contoso equips its workforce with laptops and phones leased from you. When something breaks, you take care of fixing or substituting it. When the lease expires, let\u2019s say every 2 years, you get back your hardware: Contoso then starts a new leasing with new hardware hardware equipment, and the cycle goes on until Contoso is happy with your services.<\/p>\n

The end of a lease cycle is approaching, and you are planning your hardware refresh not just for Contoso, but for many different business customers. You observed that the more the workforce is satisfied with the laptop and phone models you provide, the less they tend to call your cost center: hence you\u2019d like to poll the workforce of your various customers for making sure that you meet their preferences. That\u2019s not an easy task: you need to poll a very heterogeneous population, partitioned through multiple identity providers, in different connectivity conditions, perhaps behind firewalls whitelisting the list of websites a browser can visit, and so on and so on. Luckily you can count on the .NET Services \ud83d\ude42 the outline of the solution is as follows:<\/p>\n