Examples of using Federation server in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
A federation server performs this role automatically.
Digital signatures on security tokens are also used in theaccount partner when there is more than one federation server.
Federation servers are deployed in both networks.
Preparing and configuring a federation server and AD FS-enabled Web server for SSO access.
Federation servers authenticate requests from trusted partners based on the credentials of the partners.
This is necessary so that credentials andtokens can be successfully routed from the role service to the federation server for processing.
The federation server that is located in the corporate network of the account partner organization.
We strongly recommend that the traffic between the AD LDS server and the federation server be protected by TLS/SSL or by other means, such as Internet Protocol security IPsec.
Each federation server uses a token-signing certificate to digitally sign all security tokens that it produces.
The Federation Service node in the console tree of the Active Directory Federation Services snap-in represents thelocal Federation Service that is assigned to the federation server on which you are viewing the snap-in.
Multiple federation servers can be configured to provide fault tolerance and load balancing for a single Federation Service.
In AD FS, a collection of load-balanced federation servers, federation server proxies, or Web servers that host the AD FS Web Agent.
Federation servers can authenticate or route requests from user accounts in other organizations and from clients that can be located anywhere on the Internet.
In AD FS, a signed security token indicates that the federation server that issues the security token has successfully verified the authenticity of the federated user.
Federation server proxies provide intermediary proxy services between an Internet client and a federation server that is located behind a firewall on a corporate network.
To verify that a security token was issued by a given federation server and not modified, the federation server must have a verification certificate for the federation server that issued the security token.
The SAS Federation Server hosts these types of views, gently inserting itself between business users, analytics experts, and internal consumers of reports.
A verification certificate is stored in the trust policy andused by the federation server in one organization to verify that incoming security tokens have been issued by valid federation servers in the organization's farm and in other organizations.
A stand-alone federation server based on open standards was used, which blended seamlessly into the existing environment and integrated quickly with identity providers.
Furthermore, federation servers can be deployed in multiple organizations to facilitate business-to-business(B2B) federated transactions between partner organizations.
In this design, placing the federation server on a network that is not directly accessible from the Internet greatly reduces the risk to the federation server.
For example, if federation server A issues a security token and sends the security token to federation server B, federation server B must have a verification certificate(federation server A's token-signing certificate) for federation server A.