Clarity, Technology, and Solving Problems | PracticeThis.com
WP7 App with Key Windows Azure resources – Slides, Videos, How-To’s, and T-shooting – for quick consumption on the go.
The information in this post is based on Windows Identity Foundation Config.xml file that ships with WIF SDK.
To use the Windows Identity Foundation Framework to create an ASP.NET website that acts as a Information Card or WS-Federation relying party:
You must reference the Microsoft.IdentityModel assembly from the system.web/compilation section of your web.config.
<configuration> ... <system.web> ... <compilation> <assemblies> <add assembly="Microsoft.IdentityModel, Version=0.6.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> </assemblies> </compilation> ... </system.web> ... </configuration>
Support for relying party has been built using the following ASP.NET modules:
Depending on your scenario you will include one or more of these modules.
<configuration> ... <system.web> ... <httpModules> <add name="WSFederatedAuthenticationModule" type="Microsoft.IdentityModel.Web.WSFederatedAuthenticationModule, Microsoft.IdentityModel, Version=0.6.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/> </httpModules> ... </system.web> ... </configuration>
<configuration> ... <system.webServer> ... <modules> <add name="WSFederationAuthenticationModule" type="Microsoft.IdentityModel.Web.WSFederationAuthenticationModule, Microsoft.IdentityModel, Version=0.6.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" preCondition="managedHandler"/> </modules> ... </system.webServer> ... </configuration>
In order to use the rest of the configuration described by this file in your web.config, you must reference MicrosoftIdentityModelSection from the configSections section of your web.config.
<configuration> ... <configSections> <section name="microsoft.identityModel" type="Microsoft.IdentityModel.Web.Configuration.MicrosoftIdentityModelSection, Microsoft.IdentityModel, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/> </configSections> ... </configuration>
My colleague and a good friend, Jason Hogg, posted a call for helping to shape the guidance experience for PowerShell.
In his words:
There are two ways that we need your help: There’s a regular survey: – which this time around primarily about PowerShell. This should take about ten minutes, and will help us better understand the issues you face every day. Whether you are into PowerShell as an IT Professional or, into it as a Power Tool – any information you can provide helps. We would also like you to join our International Customer Advisory Board. This is where you can tell Microsoft what you think about using and troubleshooting our products? The Microsoft Server & Cloud International Customer Advisory Board wants to hear it. Share your opinions and help shape tomorrow’s Windows Server and System Center guidance. See http://msicab.com for more information and mail icabnom@microsoft.com to join.
There are two ways that we need your help:
There’s a regular survey: – which this time around primarily about PowerShell. This should take about ten minutes, and will help us better understand the issues you face every day. Whether you are into PowerShell as an IT Professional or, into it as a Power Tool – any information you can provide helps.
We would also like you to join our International Customer Advisory Board. This is where you can tell Microsoft what you think about using and troubleshooting our products? The Microsoft Server & Cloud International Customer Advisory Board wants to hear it. Share your opinions and help shape tomorrow’s Windows Server and System Center guidance. See http://msicab.com for more information and mail icabnom@microsoft.com to join.
I tried to come up with a quick view on available options for implementing authorization in claims aware applications.
This is what I came up with.
An app (ASPNET Web APP, WCF Service) can perform two types of access checks when using claims: