OpenID Connect Federation 1.0: Difference between revisions
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
==Context== | ==Context== | ||
Created by [[OpenID Connect 1.0]] team to specify how a Relying Party (RP) can discover metadata about an OpenID Provider (OP), and then register to obtain RP credentials. | * Created by [[OpenID Connect 1.0]] team to specify how a Relying Party (RP) can discover metadata about an OpenID Provider (OP), and then register to obtain RP credentials. | ||
* This specification describes how two entities that would like to interact can dynamically fetch and resolve trust and metadata for a given protocol through the use of third-party trust anchor. | |||
===Taxonomy=== | |||
* Trust Anchor = an entity whose main purpose is to issue statements about entities, | |||
* The [https://tcwiki.azurewebsites.net/index.php?title=Entity_Statement Entity Statement] is the core component of the Federation spec. | * The [https://tcwiki.azurewebsites.net/index.php?title=Entity_Statement Entity Statement] is the core component of the Federation spec. | ||
Revision as of 00:45, 25 May 2021
Full Name
This page describes the OpenID specification for Federation.
Context
- Created by OpenID Connect 1.0 team to specify how a Relying Party (RP) can discover metadata about an OpenID Provider (OP), and then register to obtain RP credentials.
- This specification describes how two entities that would like to interact can dynamically fetch and resolve trust and metadata for a given protocol through the use of third-party trust anchor.
Taxonomy
- Trust Anchor = an entity whose main purpose is to issue statements about entities,
- The Entity Statement is the core component of the Federation spec.