Provider Discovery - Revision history

Tom: /* Full Title or Meme */

2021-03-05T23:15:45Z

‎Full Title or Meme

Tom: /* Full Title or Meme */

2021-03-05T23:15:11Z

‎Full Title or Meme

Tom: /* Context */

2021-03-02T23:26:42Z

‎Context

Tom: /* Context */

2021-03-02T21:44:33Z

‎Context

Tom at 21:42, 2 March 2021

2021-03-02T21:42:47Z

Tom: /* References */

2021-03-02T21:40:51Z

‎References

Tom: 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..."

2021-03-02T21:31:20Z

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

New page

==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 [[Trust]]ed by users of the [[Federation]].
* [https://openid.net/specs/openid-connect-federation-1_0.html OpenID Connect Federation 1.0 - draft 10] <blockquote>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.</blockquote>

==References==
<references />
* [https://www.nist.gov/publications/nist-cloud-federation-reference-architecture The NIST Cloud Federation Reference Architecture]

[[Category:Glossary]]
[[Category:Trust]]

@@ Line 1: / Line 1: @@
 ==Full Title or Meme==
-Wherever a [[Relying Party]] or [[VerificationVerifier]] wants to get information about the provider of an [[Assertion]] they can user [[Provider Discovery]].
+Wherever a [[Relying Party]] or [[Verification|Verifier]] wants to get information about the provider of an [[Assertion]] they can user [[Provider Discovery]].
 ==Context==

@@ Line 3: / Line 3: @@
 ==Context==
 In order that an Identity, Attribute or Identity provider can expose both is principles and its capabilities to the public a [[Federation Trust Repository]] must be maintained and [[Trust]]ed by any digital endpoint that is part of the [[Ecosystem]] or Trust Federation.
 * [https://openid.net/specs/openid-connect-federation-1_0.html OpenID Connect Federation 1.0 - draft 10] <blockquote>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.</blockquote>
 ==Problem==

@@ Line 2: / Line 2: @@
 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 [[Trust]]ed by users of the [[Federation]].
 ==References==

@@ Line 11: / Line 11: @@
 ==References==
 <references />
 * [https://www.nist.gov/publications/nist-cloud-federation-reference-architecture The NIST Cloud Federation Reference Architecture]
 [[Category:Glossary]]
 [[Category:Trust]]