Difference between revisions of "Self-issued Identifier"
From MgmtWiki
(→Context) |
(→Context) |
||
| Line 6: | Line 6: | ||
* [[Distributed ID]] is a somewhat different concept in that it envisions an identity which is broken into may pieces that are hosted by many different authorities and only brought together in a [[Relying Party]] upon [[User Consent]]. The impact of that is to allow the user's [[Attribute]]s to be reference by the use with [[URL]]s that both point to the [[Attribute]]s as a part of a Token that authorizes access by the [[Relying Party]]. | * [[Distributed ID]] is a somewhat different concept in that it envisions an identity which is broken into may pieces that are hosted by many different authorities and only brought together in a [[Relying Party]] upon [[User Consent]]. The impact of that is to allow the user's [[Attribute]]s to be reference by the use with [[URL]]s that both point to the [[Attribute]]s as a part of a Token that authorizes access by the [[Relying Party]]. | ||
* The current common paradigm in open identity is for each conforming [[Relying Party]] to provide a list of [[Identifier or Attribute Provider]]s that the [[User]] could chose from to allow access. | * The current common paradigm in open identity is for each conforming [[Relying Party]] to provide a list of [[Identifier or Attribute Provider]]s that the [[User]] could chose from to allow access. | ||
| − | * The capability for | + | * The capability for dynamic registration of clients with OIDC OPs is not widely deployment today, but would become necessary with self-issued IDs. |
==Problems== | ==Problems== | ||
Revision as of 13:29, 17 December 2018
Contents
Full Title or Meme
When the Subject of an interchange is given the ability to create and manage their own Identifier and their own Identifier or Attribute Provider in support of those Identifiers and Attributes.
Context
- As a part of the effort to create OpenID Connect the option for the Subject to issue their own Identifiers was explicitly enabled.
- Distributed ID is a somewhat different concept in that it envisions an identity which is broken into may pieces that are hosted by many different authorities and only brought together in a Relying Party upon User Consent. The impact of that is to allow the user's Attributes to be reference by the use with URLs that both point to the Attributes as a part of a Token that authorizes access by the Relying Party.
- The current common paradigm in open identity is for each conforming Relying Party to provide a list of Identifier or Attribute Providers that the User could chose from to allow access.
- The capability for dynamic registration of clients with OIDC OPs is not widely deployment today, but would become necessary with self-issued IDs.
Problems
- The big problem with any sort of Self-issued Identifier is Trust where there are no standards or examples of any trust without a history of trusted behavior.
Solutions
- Define the process of creating a DID URL for the Self-issued Identifier.
- Create resolver code that could be called by any sort of Universal Resolver in the DID space.
- The Decentralized Identity Foundation has been created to enable "an open source decentralized identity ecosystem for people, organizations, apps, and devices". The have a list of areas of interest[1] that include block-chain and universal discovery which seem to be diametrically opposite of Privacy legislation like the GDPR and California Consumer Privacy Act of 2018.
References
- ↑ Decentralized Identity Foundation working groups http://identity.foundation/working-groups
