AD FS Scenarios
Business Scenarios
- Scenario: Provide
Your Active Directory Users Access to Your Claims-Aware Applications and
Services - Scenario: Provide
Your Active Directory Users Access to the Applications and Services of Other
Organizations - Scenario: Provide
Users in Another Organization Access to Your Claims-Aware Applications and
Services
Architecture/Design Scenarios
- Scenario: Implementing a Web SSO Design
- Scenario: Implementing a Federated Web SSO Design
Technical Scenarios
- Scenario: Configuring the Account Partner Organization
- Scenario: Configuring the Resource Partner Organization
- Scenario: Creating Claim Rules for a Claims Provider Trust
- Scenario: Creating Claim Rules for a Relying Party Trust
- Scenario: Setting Up a Federation Server
- Scenario: Setting Up a Federation Server Proxy
- Scenario: Preparing a New AD FS 2.0 Federation Server for Migration
- Scenario: Preparing a New AD FS 2.0 Federation Server Proxy for Migration
- Scenario: Configuring AD FS 2.0 to Consume Claims from AD FS 1.x
- Scenario: Configuring AD FS 2.0 to Send Claims to an AD FS 1.x Federation Service
- Scenario: Configuring AD FS 2.0 to Send Claims to an AD FS 1.x Claims-Aware Web Agent
Interoperability Scenarios
- Scenario: Federation with IBM Tivoli Federated Identity Manager
- Scenario: Federation with Ping Identity PingFederate
- Scenario: Federation with CA Federation Manager
- Scenario: Federation with Oracle Identity Federation
- Scenario: Federation with Shibboleth 2 and the InCommon Federation
Cloud Scenarios
- SSO from Active Directory to a Windows Azure Application
- Windows Azure AppFabric Access Control Service: WS-Federation Identity Providers
- AD FS 2.0 Federation with Microsoft Office 365 Beta