Understanding Key Concepts Before You Deploy AD FS 2.0
Applies To: Active Directory Federation Services (AD FS) 2.0
Before you begin designing your Active Directory Federation Services (AD FS) 2.0 design, we recommend that you first read about important concepts for AD FS 2.0 and become familiar with its feature set. This section of the AD FS 2.0 Design Guide and the following terminology table should provide the general information that you need to get started planning your AD FS 2.0 infrastructure.
The following terms are used often throughout this guide. They are listed here to provide you with a basic understanding for how they are used. For a more extensive listing of terms, see AD FS 2.0 Terminology in the AD FS 2.0 Product Help.
Tip
You can find additional AD FS 2.0 resource links at the AD FS 2.0 Content Map page on the Microsoft TechNet Wiki. This page is managed by members of the AD FS 2.0 Community and is monitored on a regular basis by the AD FS Product Team.
AD FS 2.0 terminology used in this guide
| AD FS 2.0 term | Definition |
|---|---|
Account partner organization |
A federation partner organization that is represented by a claims provider trust in the Federation Service. The account partner organization contains the users that will access Web-based applications in the resource partner. |
Account federation server |
The federation server in the account partner organization. The account federation server issues security tokens to users based on user authentication. The server authenticates the user, extracts the relevant attributes and group membership information out of the attribute store, packages this information into claims, and generates and signs a security token (which contains the claims) to return to the user—either to be used in its own organization or to be sent to a partner organization. |
AD FS configuration database |
A database used to store all configuration data that represents a single AD FS 2.0 instance or Federation Service. This configuration data can be stored in either a SQL Server database or using the Windows Internal Database feature included with Windows Server 2008 and Windows Server 2008 R2. You can create the AD FS configuration database for SQL Server using the Fsconfig.exe command-line tool and for Windows Internal Database using the AD FS 2.0 Federation Server Configuration Wizard. |
Claims provider |
The organization that provides claims to its users. See account partner organization. |
Claims provider trust |
In the AD FS 2.0 Management snap-in, claims provider trusts are trust objects typically created in resource partner organizations to represent the organization in the trust relationship whose accounts will be accessing resources in the resource partner organization. A claims provider trust object consists of a variety of identifiers, names, and rules that identify this partner to the local Federation Service. |
Federation metadata |
The data format for communicating configuration information between a claims provider and a relying party to facilitate proper configuration of claims provider trusts and relying party trusts. The data format is defined in Security Assertion Markup Language (SAML) 2.0, and it is extended in WS-Federation. |
Federation server |
A computer running Windows Server 2008 or Windows Server 2008 R2 that has been configured using the AD FS 2.0 Federation Server Configuration Wizard to act in the federation server role. A federation server issues tokens and serves as part of a Federation Service. |
Federation server proxy |
A computer running Windows Server 2008 or Windows Server 2008 R2 that has been configured using the AD FS 2.0 Federation Server Proxy Configuration Wizard to act as an intermediary proxy service between an Internet client and a Federation Service that is located behind a firewall on a corporate network. |
Primary federation server |
A computer running Windows Server 2008 or Windows Server 2008 R2 that has been configured in the federation server role using the AD FS 2.0 Federation Server Configuration Wizard and has a read/write copy of the AD FS configuration database. The primary federation server is created when you use the AD FS 2.0 Federation Server Configuration Wizard and select the option to create a new Federation Service and make that computer the first federation server in the farm. All other federation servers in this farm must replicate changes made on the primary federation server to a read-only copy of the AD FS configuration database that is stored locally. The term “primary federation server” does not apply when the AD FS configuration database is stored in an SQL database as all federation servers can equally read and write to a configuration database stored on a SQL Server. |
Relying party |
The organization that receives and processes claims. See resource partner organization. |
Relying party trust |
In the AD FS 2.0 Management snap-in, relying party trusts are trust objects typically created in:
A relying party trust object consists of a variety of identifiers, names, and rules that identify this partner or web-application to the local Federation Service. |
Resource federation server |
The federation server in the resource partner organization. The resource federation server typically issues security tokens to users based on a security token that is issued by an account federation server. The server receives the security token, verifies the signature, applies claim rule logic to the unpackaged claims to produce the desired outgoing claims, generates a new security token (with the outgoing claims) based on information in the incoming security token, and signs the new token to return to the user and ultimately to the Web application. |
Resource partner organization |
A federation partner that is represented by a relying party trust in the Federation Service. The resource partner issues claims-based security tokens that contains published Web-based applications that users in the account partner can access. |
Overview of AD FS 2.0
AD FS 2.0 is an identity access solution that provides client computers (internal or external to your network) with seamless SSO access to protected Internet-facing applications or services, even when the user accounts and applications are located in completely different networks or organizations.
When an application or service is in one network and a user account is in another network, typically the user is prompted for secondary credentials when he or she attempts to access the application or service. These secondary credentials represent the user's identity in the realm where the application or service resides. They are usually required by the Web server that hosts the application or service so that it can make the most appropriate authorization decision.
With AD FS 2.0, organizations can bypass requests for secondary credentials by providing trust relationships (federation trusts) that these organizations can use to project a user's digital identity and access rights to trusted partners. In this federated environment, each organization continues to manage its own identities, but each organization can also securely project and accept identities from other organizations.
For more general information about AD FS 2.0, see the AD FS 2.0 Product Help (https://go.microsoft.com/fwlink/?LinkId=148504).