Checklist: Implementing a Web SSO Design
Applies To: Active Directory Federation Services (AD FS) 2.0
This parent checklist includes cross-reference links to important concepts about the Web Single-Sign-On (SSO) design for Active Directory Federation Services (AD FS) 2.0. 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 complete the tasks in the subordinate checklist so that you can proceed with the remaining tasks in this checklist.
.gif)
Checklist: Implementing a Web SSO Design
| Task | Reference | |||
|---|---|---|---|---|
.gif) |
Review important concepts about the Web SSO design and determine which AD FS 2.0 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), attribute store, and client requirements for deploying AD FS 2.0 in your organization. |
|||
|
According to your design plan, install one or more federation servers in the corporate network or in the perimeter network. Note The Web SSO design requires only one federation server to function successfully. A single federation server acts in both the claims provider role and the relying party role.
|
|||
|
(Optional) Determine whether or not your organization needs a federation server proxy in the perimeter network. |
|||
|
Depending on your Web SSO design plan and how you intend to use it, add the appropriate attribute store, relying party trusts, claims, and claim rules to the Federation Service. |
|||
|
If you are an administrator in the resource partner organization, claims-enable your Web browser application, Web service application, or Microsoft® Office SharePoint® Server 2007 application using WIF and the WIF SDK. Note |
.gif)
Note.gif)
.gif)