Checklist: Implementing a Federated Web SSO Design
Applies To: Windows Server 2008
This parent checklist includes cross-reference links to important concepts about the Federated Web Single-Sign-On (SSO) 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.
.gif)
Checklist: Implementing a Federated Web SSO Design
| Task | Reference | |||
|---|---|---|---|---|
.gif) |
Review important concepts and examples for the Federated Web SSO 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. |
|||
|
Review the hardware, software, certificate, Domain Name System (DNS), account store, and client requirements for deploying AD FS in both partner organizations. |
|||
|
According to your design plan, install one or more federation servers in each partner organization.
|
|||
|
(Optional) Determine whether or not your organization needs a federation server proxy. If your design plan calls for a proxy, you can install one or more federation server proxies in each partner organization. |
|||
|
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.
|
|||
|
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. |
|||
|
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.
|
.gif)
.gif)
Note.gif)