Fabrikam Jets - Integrating Codename "Dallas" with AppFabric Access Control
- Posted: Dec 03, 2009 at 1:13 PM
- 8,551 Views
- 2 Comments
This screencast shows how AppFabric Access Control (AC) can be used to provide identity
federation, trust delegation, service authorization and integration with Active
Directory Federation Services (ADFS), to control access to services based on
Windows Azure.
In the demo, Fabrikam Jets uses the Dallas Portal, AC and ADFS to grant employees of Contoso Marketing access to Microsoft Codename "Dallas" at Fabrikam's expense, using Windows authentication, without exposing Fabrikam's Dallas account keys. It also shows how Fabrikam can revoke the privilege later.
The source code for this example is now available soon on this MSDN Code Gallery page.
Note: The example has been updated to work with the V1 version of AppFabric Access Control. There were two changes from the CTP version to V1 that made the update necessary: 1) V1 uses version 0.9 of the WRAP protocol, instead of version 0.8, and 2) the issuer name generated by V1 is the base URI of the STS endpoint for the service namespace, instead of the full URI. The screen cast has not yet been updated, and still shows the user providing the full URI of the STS endpoint as the key description, rather than the base URI. In all other respects, however, it remains accurate.
In the demo, Fabrikam Jets uses the Dallas Portal, AC and ADFS to grant employees of Contoso Marketing access to Microsoft Codename "Dallas" at Fabrikam's expense, using Windows authentication, without exposing Fabrikam's Dallas account keys. It also shows how Fabrikam can revoke the privilege later.
The source code for this example is now available soon on this MSDN Code Gallery page.
Note: The example has been updated to work with the V1 version of AppFabric Access Control. There were two changes from the CTP version to V1 that made the update necessary: 1) V1 uses version 0.9 of the WRAP protocol, instead of version 0.8, and 2) the issuer name generated by V1 is the base URI of the STS endpoint for the service namespace, instead of the full URI. The screen cast has not yet been updated, and still shows the user providing the full URI of the STS endpoint as the key description, rather than the base URI. In all other respects, however, it remains accurate.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
The example is publicly available, and can be used with any AC service namespace. The FabrikamJets service namespace used in the screen cast remains private, however, in the interest of preserving the behavior shown in the screen cast for the benefit of those who are interested in learning about it.
buenos dias
solicito el favor y me envies unos videos de c# estoy empezando a aprender a programar en este lenguaje y necesito de toda la ayuda posible para aprender
Remove this comment
Remove this thread
close