Planning Partner Organization Deployments
Updated: December 15, 2006
Applies To: Windows Server 2003 R2
When you plan for cross-organizational (federation-based) collaboration using Active Directory Federation Services (ADFS), you first determine if your organization will host a Web resource to be accessed by other organizations across the Internet or if you will provide access to the Web resource for employees in your organization. This determination affects how you deploy ADFS, and it is fundamental in the planning of your ADFS infrastructure.
|Make sure that the role that your organization plays in the federation agreement is clearly understood by all parties.|
For the federation designs Federated Web SSO design and Federated Web SSO with Forest Trust design, ADFS uses terms such as "account partner" and "resource partner" to help differentiate the organization that hosts the accounts (the account partner) from the organization that hosts the Web-based resources (the resource partner).
"Account partner" and "resource partner" terminology is not applicable in the Web SSO design because one federation server acts in both the account partner role and the resource partner role, and there is no identification of two distinct partners in the Federation Service.
The following sections explain some of the ADFS partner organization concepts. They also contain links to topics in the Active Directory Federation Services Deployment Guide that contain information about setting up and configuring account partners and resource partners based on your ADFS deployment goals.
Planning the account partner deployment
An account partner represents the organization in the federation trust relationship that physically stores user accounts in either an Active Directory store or an Active Directory Application Mode (ADAM) store. The Federation Service in the account partner organization authenticates local users and creates security tokens that are used by the resource partner in making authorization decisions.
In scenarios in which you need to provide your users with access to multiple federated applications—when each application is hosted by a different organization—you can configure the account Federation Service so that you can deploy multiple resource partners.
For more information about how to set up and configure an account partner organization, see Checklist: Configuring the account partner organization.
Planning the resource partner deployment
The resource partner organization represents the organization whose ADFS-enabled Web servers are protected by the resource-side Federation Service. The Federation Service at the resource partner uses the security tokens that are produced by the account partner to make authorization decisions for ADFS-enabled Web servers that are located in the resource partner.
In scenarios in which you need to provide access to federated applications to many different users—when some users reside in different organizations—you can configure the resource Federation Service so that you can deploy multiple account partners.
For more information about how to set up and configure a resource partner in the account Federation Service, see Checklist: Configuring the resource partner organization.