!!! Overview
[{$pagename}] as we use it is [Federated Identity Management]

[{$pagename}] is a process that allows for the conveyance of identity and [authentication] information across a set of networked systems. In a [{$pagename}] scenario, the [verifier] or [Credential Service Provider] is known as the [Identity Provider (IDP)], or [IDP]. The [Relying Party], or [RP], is the party that receives the [Federated Identity]. ([NIST.SP.800-63C])

[{Image src='Federation/federation.png' caption='Federation' align=left width=1024 height=768 style='font-size: 120%}]. \\

A [{$pagename}] occurs when one system [trust]s an [Identity Provider (IDP)] to [authenticate] a [digital Identity]

Some people only refer to [{$pagename}] when it is [Cross-domain authentication]. 

Others prefer to say anytime the [authentication Method] is not on the same system it is a [{$pagename}].

Generally, any [RP] which accepts the [credential]'s from an [Identity Provider (IDP)] is part of a [{$pagename}]. 

The [Identity Provider (IDP)] is the Primary Domain and the other security domains that [trust]s the [Identity Provider (IDP)] to [authenticate] a [digital Identity] are referred to as [Relying Party] ([RP])/[Service Providers|SP] ([SP]). 

[Credential] information is typically __NOT__ passed between the parties.

[Digital Identity] data may be passed between these parties.


[{$pagename}] is a form of [Identity Correlation] and/or [Identity Broker]

Often [Tokens] are used in [{$pagename}] by a system called a [Security Token Service] ([STS]) which would typically be in or strongly associated with the [Identity Provider (IDP)]

!! [Federation Models]
[Federation Models] provides an overview of and requirements for common identity [Federation Models] currently in use. In each model, relationships are established between members of the federation in several different ways.

!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]