Difference between revisions of "Federation"
From MgmtWiki
(→Solution) |
(→Context) |
||
| Line 2: | Line 2: | ||
Wherever a collection of [[Web Site]]s band together to create a common set of rules that all agree to be bound by. | Wherever a collection of [[Web Site]]s band together to create a common set of rules that all agree to be bound by. | ||
==Context== | ==Context== | ||
| + | Federation allow the creation of in [[Identifier]]. [[Ecosystem]] to be implemented for the imposition of policies that apply to all members of the federation. | ||
==Problem== | ==Problem== | ||
Revision as of 10:49, 10 April 2021
Full Title or Meme
Wherever a collection of Web Sites band together to create a common set of rules that all agree to be bound by.
Context
Federation allow the creation of in Identifier. Ecosystem to be implemented for the imposition of policies that apply to all members of the federation.
Problem
Solution
In order that a Federation can expose both is principles and its membership to the public a Federation Trust Repository must be maintained and Trusted by users of the Federation.
- OpenID Connect Federation 1.0 - draft 10
The OpenID Connect standard specifies how a Relying Party (RP) can discover metadata about an OpenID Provider (OP), and then register to obtain RP credentials. The Provider Discovery and registration process does not involve any mechanisms of dynamically establishing trust in the exchanged information, but instead rely on out-of-band trust establishment. In an identity federation context, this is not sufficient. The participants of the federation must be able to trust information provided about other participants in the federation. OpenID Connect Federations specifies how trust can be dynamically obtained by resolving trust from a common trusted third party.
