Interoperating with AD FS 1.x
Applies To: Active Directory Federation Services (AD FS) 2.0
For interoperability between Active Directory Federation Services (AD FS) 2.0 and AD FS 1.x, complete one or more of the following tasks, depending on the needs of your organization:
Plan for interoperability between AD FS 2.0 and previous versions of AD FS, and learn more about the Name ID claim type. For more information, see Planning for Interoperability with AD FS 1.x.
If you will be sending claims from an AD FS 2.0 Federation Service that can be consumed by an AD FS 1.x Federation Service, see Checklist: Configuring AD FS 2.0 to Send Claims to an AD FS 1.x Federation Service.
If you will be sending claims from an AD FS 2.0 Federation Service that can be consumed by an application that is hosted by a Web server running the AD FS 1.x claims-aware Web agent, see Checklist: Configuring AD FS 2.0 to Send Claims to an AD FS 1.x Claims-Aware Web Agent.
If you will be sending claims from an AD FS 1.x Federation Service to be consumed by an AD FS 2.0 Federation Service, see Checklist: Configuring AD FS 2.0 to Consume Claims from AD FS 1.x.
Differences between an AD FS 1.x Federation Service and an AD FS 2.0 Federation Service
Although most of the AD FS 1.x Federation Service settings work in a similar manner as the AD FS 2.0 Federation Service settings, some setting names have changed. The following table lists the names of settings for an AD FS 1.x Federation Service and their equivalent names for an AD FS 2.0 Federation Service.
| AD FS 1.x Federation Service setting | Equivalent AD FS 2.0 Federation Service setting |
|---|---|
Account Partner |
Claims provider trust |
Resource Partner |
Relying party trust |
Application |
Relying party trust |
Application Properties |
Relying party trust properties |
Application URL |
Relying party identifier and WS-Federation Passive Endpoint URL |
Federation Service URI |
Federation Service identifier |
Federation Service endpoint URL |
WS-Federation Passive Endpoint URL |