Where to place a federation server
Applies To: Windows Server 2003 R2
As a security best practice, place federation servers in front of a firewall and connect them to the corporate network to prevent exposure from the Internet. This is important because federation servers have full authorization to grant security tokens. Therefore, they should have the same protection as a domain controller. If a federation server is compromised, a malicious user has the ability to issue full access tokens to all Web applications and federation servers that are protected by Active Directory Federation Services (ADFS) in all resource partner organizations.
Note
As a security best practice, avoid having your federation servers directly accessible on the Internet. Consider giving your federation servers direct Internet access only when you are setting up a test lab environment or when your organization does not have a perimeter network.
For typical corporate networks, an intranet-facing firewall is established between the corporate network and the perimeter network, and an Internet-facing firewall is often established between the perimeter network and the Internet. In this situation, the federation server sits inside the corporate network, and it is not directly accessible by Internet clients.
Note
Clients that are connected to the corporate network can communicate directly with the federation server through Windows Integrated authentication.
A federation server proxy should be placed in the perimeter network before you configure your firewall servers for use with ADFS. For more information, see Where to place a federation server proxy.
Configuring your firewall servers for a federation server
So that the federation servers can communicate directly with federation server proxies, the intranet firewall server must be configured to allow Secure Hypertext Transfer Protocol (HTTPS) traffic from the federation server proxy to the federation server. This is a requirement because the intranet firewall server must publish the federation server using port 443 so that the federation server proxy in the perimeter network can access the federation server.
Note
All communications to and from clients also occur over HTTPS.
In addition, the intranet-facing firewall server, such as a server running Internet Security and Acceleration (ISA) Server, uses a process known as server publishing to distribute Internet client requests to the appropriate corporate federation servers. This means that you must manually create a server publishing rule on the intranet server running ISA Server that publishes the clustered federation server Uniform Resource Locator (URL), for example, https://fs.adatum.com.
For more information about how to configure server publishing in a perimeter network, see Where to place a federation server proxy. For information about how to configure ISA Server to publish a server, see Create a Secure Web Publishing Rule (https://go.microsoft.com/fwlink/?LinkId=75182).
If you are using the Federated Web SSO with Forest Trust design, be sure to open the ports that are required for setting up a one-way, forest trust. For more information about network ports that trusts use, see Domain and Forest Trust Tools and Settings (https://go.microsoft.com/fwlink/?LinkId=79059).