Checklist: Configuring the Resource Partner Organization

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

The resource partner organization contains the Web servers hosting the Web-based applications that will be accessed by users in the account partner. Administrators in this organization must use the AD FS 2.0 Management snap-in to create claims provider trusts to represent their trust relationships with account partner organizations. In turn, the account partner administrator must create relying party trusts for each account partner organization that they want to trust.

This checklist includes the tasks that are necessary for deploying Active Directory Federation Services (AD FS) 2.0 in the resource partner organization. It also includes tasks for configuring the components that are required to establish one-half of a federation partnership.

If you are deploying a Web SSO Design, you do not have to follow this checklist. However, you do have to complete the tasks in this checklist to successfully deploy a Federated Web SSO Design.

Important

Make sure that the administrator of the account partner organization follows the guidance in Checklist: Configuring the Account Partner Organization to ensure that all necessary deployment tasks will be completed to successfully create the second half of the federation partnership

Note

Complete the tasks in this checklist in order. When a reference link takes you to a procedure, return to this topic after you complete the steps in that procedure so that you can proceed with the remaining tasks in this checklist.

Checklist: Configuring the resource partner organization

	Task	Reference
	If you have an existing AD FS 1.0 or 1.1 deployment in your production environment today, see the link to the right for information about how to migrate settings from your current Federation Service to a new AD FS 2.0 Federation Service. If you are deploying AD FS for the first time in your organization using AD FS 2.0, you can skip this step and continue to the next task in this checklist for information about how to set up a new resource partner organization.	Planning a Migration to AD FS 2.0
	Based on your deployment goals, review information about the components that are required to provide users with access to the federated applications that you host in your organization.	Provide Your Active Directory Users Access to Your Claims-Aware Applications and Services Provide Your Active Directory Users Access to the Applications and Services of Other Organizations Provide Users in Another Organization Access to Your Claims-Aware Applications and Services
	Determine which AD FS 2.0 design this resource partner organization will be associated with.	Web SSO Design Federated Web SSO Design
	Review the different application types, and decide which application to deploy.	Determine Your Federated Application Strategy in the Resource Partner
	Before you begin deploying your AD FS 2.0 servers, review the; 1.) advantages and disadvantages of choosing either Windows Internal Database (WID) or SQL Server to store the AD FS configuration database 2.) AD FS 2.0 deployment topology types and their associated server placement and network layout recommendations.	Determine Your AD FS 2.0 Deployment Topology AD FS 2.0 Deployment Topology Considerations
	Review AD FS 2.0 capacity planning guidance to determine the proper number of federation server and federation server proxy servers you should use in your production environment.	Planning for AD FS 2.0 Server Capacity
	To effectively plan and implement the physical topology for the resource partner deployment, determine whether your AD FS 2.0 design requires one or more federation servers, or federation server proxies.	Checklist: Setting Up a Federation Server Checklist: Setting Up a Federation Server Proxy
	Determine whether you need an attribute store in the resource partner organization. If you need an attribute store resource partner, add the attribute store with the AD FS 2.0 Management snap-in.	The Role of Attribute Stores Add an Attribute Store
	If you will need to send claims to or consume claims from an account partner who is using either an AD FS 1.0 or 1.1 Federation Service, see the link to the right for information about how to configure AD FS 2.0 to interoperate with previous versions of AD FS. If the account partner organization is also using AD FS 2.0 to send or consume claims to your organization, you can skip this step and continue with the next task in this checklist.	Planning for Interoperability with AD FS 1.x
	After you deploy the first federation server in the resource partner organization, create a claims provider trust relationship by using the AD FS 2.0 Management snap-in. You can create a claims provider trust by entering data about an account partner manually or by using a federation metadata URL that the administrator of the account partner organization provides to you. You can use the federation metadata to retrieve the data for the resource partner automatically. Note If the account partner publishes its federation metadata or can provide a file copy of it for you to use, we recommend that you retrieve the data automatically because it can save time.	Create a Claims Provider Trust Manually Create a Claims Provider Trust Using Federation Metadata
	Depending on the needs of your organization, create one or more claim rule sets for each claims provider trust that is specified in the AD FS 2.0 Management snap-in so that incoming claims will be passed through, transformed, or mapped appropriately to corresponding claims in the resource partner.	Checklist: Creating Claim Rules for a Claims Provider Trust
	(Optional) A claim description may have to be created if one does not already exist that will fulfill the needs of your organization. AD FS 2.0 ships with a default set of claim descriptions that are exposed in the AD FS 2.0 Management snap-in.	Add a Claim Description