Difference between revisions of "Federation"
From MgmtWiki
(→Solution) |
(→References) |
||
| Line 11: | Line 11: | ||
==References== | ==References== | ||
<references /> | <references /> | ||
| − | * [https://www.nist.gov/ | + | * [https://www.nist.gov/publications/nist-cloud-federation-reference-architecture The NIST Cloud Federation Reference Architecture] |
[[Category:Glossary]] | [[Category:Glossary]] | ||
[[Category:Trust]] | [[Category:Trust]] | ||
Revision as of 16:40, 31 May 2020
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
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 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.
