Windows Identity Foundation SDK

Overview
The Windows Identity Foundation SDK provides templates for use with Visual Studio and code samples. This download requires the Windows Identity Foundation runtime be present.

Read more: MS Download

Posted via email from .NET Info

Windows Identity Foundation (WIF) SDK Help Overhaul

• Overview
  • Identity Challenges – SSO, Identity Flow, Fine Grained Authorization (Changed from: Identity Silos)
  • The Claims-Based Identity Model
  • Solution Concept (Changed from: Basic Scenario)
  • Security Token Service
  • Relying Party
  • Solution Implementation Overview (Changed from: Federation Scenario)
  • Fast track (How to use this content)
• Getting Started
  • Windows Identity Foundation SDK - Download and Installation of runtime and dev tools (External)
  • Windows Identity Foundation Download and Installation of runtime only (External)
  • Requirements (Changed from Windows Identity Foundation SDK)
  • How to: Build an ASP.NET Relying Party Application
  • How to: Build a WCF Relying Party Application
• Product Features
  • What is Windows Identity Foundation?
  • Expose claims to ASP.NET applications and WCF services via Integration with IIdentity and IPrincipal
  • Visual Studio Templates
  • Administrative trust management using FedUtil tool
  • Federated Sign In ASP.NET control
  • Translate between claims and NT tokens
  • Support for Identity Delegation Scenario via ActAs token
  • Supports the WS-Trust protocol, Active Profile
  • Supports WS-Federation, Passive profile
  • Glossary
• Architecture
  • The Claims-Based Identity Model
  • Integration with IIdentity and IPrincipal
  • How WIF Processes Requests– (Changed from: Building Relying Party Applications)
  • Security Token Service
  • Relying Party
  • What is an IP-STS and what is a RP-STS?
  • WS-Federated Authentication Module Overview
  • Session Management
  • IssuerNameRegistry
  • Claims to Windows Token Service (c2WTS) Overview
  • ClaimsAuthenticationManager, ClaimsAuthorizationManager, and OriginalIssuer
  • Claims Issuance Pipeline
  • Token Handlers
  • Built-In Token Handlers
• Application Scenarios and Solutions
  • Integrating WIF with ASP.NET web applications (Changed from: Building ASP.NET Relying Party Applications)
    • How to: Build an ASP.NET Relying Party Application
    • How To: Establishing Trust from an ASP.NET Relying Party Application to an STS using FedUtil
    • How To: Establishing Trust from an ASP.NET Relying Party Application to an STS using the FederatedPassiveSignIn
    • Sample: Simple Claims Aware Web Application
    • Sample: Claims based Authorization
    • Sample: Using Claims In IsInRole
  • Integrating WIF with WCF services (Changed from: Building WCF Relying Party Applications)
    • WCF Application Compatibility
    • WCF: WSTrustChannelFactory and WSTrustChannel
    • WCF: Built-in Bindings Overview
    • How to: Build a WCF Relying Party Application
    • How To: Establishing Trust from a WCF Relying Party Service to an STS using FedUtil
    • Sample: Simple Claims Aware Web Service
    • Sample: Claims based Authorization
    • Sample: Using Claims In IsInRole
  • Building Security Token Services (STS) (Changed from: Building an STS)
    • How to: Build Passive Profile (WS-Federation) STS – For ASP.NET (Changed from: How to: Build an ASP.NET STS)
    • How to: Build Active Profile (WS-Trust) STS – For WCF (Changed from: How to: Build a WCF STS)
• WIF Anatomy
  • Identification (how a client identifies itself)
    • WIF Client

Read more: Alik Levin's

Posted via email from .NET Info

Windows Identity Foundation (WIF) By Example Part I – How To Get Started.

This post reflects on the steps I needed to perform to create my first Windows Identity Foundation (WIF) application from zero to Hello World. It can serve as a bootstrap for starting developing Claims-Aware ASP.NET application using Windows Identity Foundation (WIF).
This post quickly goes through preparing the development environment for using Windows Identity Foundation (WIF) and it walks through creating basic simple Claims-Aware web site.
Summary of steps:
Step 1 – Prepare Development Environment
Step 2 – Configure IIS7 to use SSL
Step 3 – Create Claims-Enabled Web Site
Step 4 - Add local STS (Security Token Service)
Step 5 – Configure IIS to load User Profile
Step 6 – Test Your Work
Rest of the post is detailed explanation for each step followed by the resources in the end.
Step 1 – Prepare Development Environment
Have VS2010 installed.
Use Web Platform Installer available here to configure your dev machine. Tick all options on for Web Server and for Frameworks and Runtimes unless it completely sounds off like CGI.
Read more: Alik Levin's

Posted via email from .NET Info