Deploying Federation Server Proxies
Updated: December 15, 2006
Applies To: Windows Server 2003 R2
To deploy federation server proxies, complete each of the tasks in Checklist: Installing a federation server proxy.
|When you use this checklist, we strongly recommend that you first read the references to federation server proxy planning guidance (in the ADFS Design Guide) before continuing to the procedures for configuring the servers. Following the checklist in this way will help provide a better understanding of the full design and deployment story for federation server proxies.|
About federation server proxies
Federation server proxies are computers running Windows Server 2003 R2 that are configured to host the Federation Service Proxy component of Active Directory Federation Services (ADFS). You can use federation server proxies in your organization to provide intermediary services between an Internet client and a federation server that is behind a firewall on the corporate network.
|Although the Federation Service and the Federation Service Proxy components cannot be installed on the same computer, a federation server can perform federation server proxy functionality. For more information, see When to create a federation server.|
The act of installing the Federation Service Proxy on a computer makes that computer a federation server proxy. It also makes the Active Directory Federation Services snap-in available on that computer on the Administrative Tools menu so that you can specify the following:
Which Federation Service the federation server proxy should route authentication requests to. You specify this location by typing the path for the Federation Service Uniform Resource Locator (URL).
The client authentication certificate that makes it possible for the federation server proxy to authenticate to the Federation Service. You can configure which client authentication certificates will be accepted by the Federation Service on the FSP Certificates tab in the properties of the Trust Policy Folder.
After you specify the Federation Service URL and the correct client authentication certificate, the federation server proxy is bound to that Federation Service. As part of this binding, a federation server proxy is trusted by the Federation Service so that the federation server can hand out certain privileged security tokens that originate from the Federation Service.
Locations of customized ASP.NET Web pages for client logon, logoff, and account partner discovery that enable interaction with a client. These pages provide a convenient way to differentiate the sign-in experience for users in your intranet as opposed to users on the Internet.
Note You can also configure these settings in the Web.config file on each federation server proxy.
Federation server proxies also send cookies to external clients when necessary to facilitate the single-sign-on (SSO) process. These cookies include authentication cookies, account partner cookies, and sign-out cookies.
A federation server proxy implements the sign-on and sign-out messages that are described in the WS-Federation Passive Requestor Profile (WS-F PRP) protocol specification.