Checklist: Implementing a Federated Web SSO with Forest Trust Design

Applies To: Windows Server 2008

This parent checklist includes cross-reference links to important concepts about the Federated Web Single-Sign-On (SSO) with Forest Trust design. It also contains links to subordinate checklists that will help you complete the tasks that are required to implement this design.

Note

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

Checklist: Implementing a Federated Web SSO with Forest Trust Design

	Task	Reference
	Review important concepts and examples for the Federated Web SSO with Forest Trust design and determine which Active Directory Federation Services (AD FS) deployment goals you can use to customize this design to meet the needs of your organization.	Federated Web SSO with Forest Trust Design Federated Web SSO with Forest Trust Example Identifying Your AD FS Deployment Goals
	Review the requirements for enabling the Federated Web SSO with Forest Trust design in both the account partner organization and the resource partner organization.	When to Enable Windows Trusts
	Review the hardware, software, certificate, Domain Name System (DNS), account store, and client requirements for deploying AD FS in both partner organizations.	Appendix A: Reviewing AD FS Requirements
	According to your design plan, install one or more federation servers in each partner organization. Note The Federated Web SSO with Forest Trust design requires at least one federation server in the account partner and at least one federation server in the resource partner.	Checklist: Installing a Federation Server
	(Optional) Determine whether or not your organization needs a federation server proxy. If your design plan calls for a federation server proxy, you can install one or more federation server proxies in each partner organization.	Checklist: Installing a Federation Server Proxy
	If you are an administrator in the resource partner organization, install one or more AD FS-enabled Web servers to host your preferred federated application using the appropriate AD FS Web Agent. Note The account partner administrator does not have to complete the following checklist.	Checklist: Installing an AD FS-Enabled Web Server
	According to your design plan, share certificates, configure clients, and configure the Federation Service in both partner organizations so that they can communicate over a federation trust.	Checklist: Configuring the Account Partner Organization Checklist: Configuring the Resource Partner Organization
	To enable the Federated Web SSO with Forest Trust scenario, complete the appropriate procedure in the account Federation Service and in the resource Federation Service. Note You must enable the Windows trust option in both the account Federation Service and in the resource Federation Service. If only one partner has this option enabled, this design will not function.	Configure an Account Partner to Use Windows Trust Configure a Resource Partner to Use Windows Trust
	If you are an administrator in the resource partner organization, install either a claims-aware application or a Windows NT token–based application, or both, using the appropriate checklist. Note The account partner administrator does not have to complete either of the following checklists.	Checklist: Installing a Claims-Aware Application Checklist: Installing a Windows NT Token-Based Application