Difference between revisions of "Provider Discovery"

From MgmtWiki
Jump to: navigation, search
(Created page with "==Full Title or Meme== Wherever a Relying Party or Verifier wants to get information about the provider of an Assertion they can user Provider Discovery. ==Con...")
 
(References)
Line 11: Line 11:
 
==References==
 
==References==
 
<references />
 
<references />
 +
* A [[Federation]] will typically have a [[Trust Authority]] to provide signed certifications or credentials. It should also provide an endpoint for discovery.
 
* [https://www.nist.gov/publications/nist-cloud-federation-reference-architecture The NIST Cloud Federation Reference Architecture]  
 
* [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 14:40, 2 March 2021

Full Title or Meme

Wherever a Relying Party or Verifier wants to get information about the provider of an Assertion they can user Provider Discovery.

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 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.

References