다음을 통해 공유

Planning for Interoperability with AD FS 1.x

  • 아티클

Applies To: Active Directory Federation Services (AD FS) 2.0

Active Directory Federation Services (AD FS) 2.0 federation servers can interoperate with both an AD FS 1.0 (installed with Windows Server 2003 R2) Federation Service and an AD FS 1.1 (installed with Windows Server 2008 or Windows Server 2008 R2) Federation Service. Any of the following interoperability combinations are supported:

Note

AD FS 2.0 does not support or interoperate with the AD FS 1.x Windows NT token–based Web agent.

An AD FS 1.x-compatible claim is a claim that can be sent by an AD FS 2.0 Federation Service and understood by an AD FS 1.x Federation Service. So that an AD FS 1.x Federation Service can consume the claims that an AD FS 2.0 Federation Service sends, a Name Identifier (ID) claim type must be sent.

Understanding the Name ID claim type

The Name ID claim type is the equivalent of the identity claim type that AD FS 1.x uses. It must be used whenever you want to interoperate with AD FS 1.x. The Name ID claim type enables either an AD FS 1.x Federation Service or the AD FS 1.x claims-aware Web agent to consume claims that AD FS 2.0 sends, as long as these claims are sent in one of the Name ID formats in the following table.

Name ID format Corresponding URI

AD FS 1.x Email Address

https://schemas.xmlsoap.org/claims/EmailAddress

AD FS 1.x Email UPN

https://schemas.xmlsoap.org/claims/UPN

Common Name

https://schemas.xmlsoap.org/claims/CommonName

Group

https://schemas.xmlsoap.org/claims/Group

Only one Name ID claim in the appropriate format must be sent. When that criterion is satisfied, many other claims may be sent as well, assuming that they conform to the restrictions described in the table.

Note

An AD FS 1.x Federation Service can interpret only incoming claim types that begin with the Uniform Resource Identifier (URI) of https://schemas.xmlsoap.org/claims/.