Distributed Identity - Revision history

Tom: /* Context */

2025-02-27T04:58:07Z

‎Context

2025-02-27T02:25:19Z

‎Context

2025-02-27T02:18:43Z

‎Context

2018-12-22T18:20:25Z

‎Context

2018-12-22T18:15:58Z

‎References

2018-11-06T23:36:55Z

‎Context

2018-11-06T23:36:14Z

‎Context

2018-11-06T23:35:42Z

‎Context

2018-09-07T23:42:34Z

‎Context

2018-08-06T16:44:46Z

‎Solutions

@@ Line 10: / Line 10: @@
 * Interestingly [https://www.ibm.com/support/knowledgecenter/en/SSGMCP_5.4.0/security/cics/idprop_intro.html IBM has offered support for Distributed Identity] in their CICS for several generations now. This is similar to the federated identity supported by [https://en.wikipedia.org/wiki/Active_Directory_Federation_Services Microsoft ADFS].
 * The current most common protocol for some sort of a [[Decentralized Identifier]] was [[OpenID Connect]] which included [[Self-issued Identity]], but that concept never succeeded in the marketplace.
-* Now other organizations believe that they can succeed the [[Self-Sovereign Identity]] where the OpenID foundation failed.
+* Now other organizations believe that they can succeed the [[Self-Sovereign Identity]] where the OpenID foundation failed by merging OID with [[Decentralized Identifier]] and [[Verifiable Presentation]] data formats.
 ==Problems==

@@ Line 9: / Line 9: @@
 ** It also required the user to pre-register with one or more of those providers, typically one of the big social sites, like: Google, Microsoft or Facebook.
 * Interestingly [https://www.ibm.com/support/knowledgecenter/en/SSGMCP_5.4.0/security/cics/idprop_intro.html IBM has offered support for Distributed Identity] in their CICS for several generations now. This is similar to the federated identity supported by [https://en.wikipedia.org/wiki/Active_Directory_Federation_Services Microsoft ADFS].
-* The current most common protocol for some sort of a [[Distributed Identifier]] was [[OpenID Connect]] which included [[Self-issued Identity]], but that concept never succeeded in the marketplace.
+* The current most common protocol for some sort of a [[Decentralized Identifier]] was [[OpenID Connect]] which included [[Self-issued Identity]], but that concept never succeeded in the marketplace.
 * Now other organizations believe that they can succeed the [[Self-Sovereign Identity]] where the OpenID foundation failed.

@@ Line 9: / Line 9: @@
 ** It also required the user to pre-register with one or more of those providers, typically one of the big social sites, like: Google, Microsoft or Facebook.
 * Interestingly [https://www.ibm.com/support/knowledgecenter/en/SSGMCP_5.4.0/security/cics/idprop_intro.html IBM has offered support for Distributed Identity] in their CICS for several generations now. This is similar to the federated identity supported by [https://en.wikipedia.org/wiki/Active_Directory_Federation_Services Microsoft ADFS].
-* The current most common protocol for some sort of a [[Distributed Identity]] was [[OpenID Connect]] which included [[Self-issued Identity]], but that concept never succeeded in the marketplace.
+* The current most common protocol for some sort of a [[Distributed Identifier]] was [[OpenID Connect]] which included [[Self-issued Identity]], but that concept never succeeded in the marketplace.
-* Now other organizations believe that they can succeed where the OpenID foundation failed.
+* Now other organizations believe that they can succeed the [[Self-Sovereign Identity]] where the OpenID foundation failed.
 ==Problems==

@@ Line 3: / Line 3: @@
 ==Context==
 * [[Decentralized ID]] is a somewhat different concept in that it envisions an identity which is centralized with the user rather than with a central authority.
 * The current 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.

@@ Line 16: / Line 16: @@
 ==Solutions==
 *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<ref>Decentralized Identity Foundation working groups http://identity.foundation/working-groups</ref> 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]].
-*In this wiki the IAP ([[Identifier or Attribute Provider]]) supplies only the [[Data Category]] that has [[User Consent]]. To get all of those categories that the [[Relying Party]] requires, the request needs to go to a [[User Agent]] that is able to release the data held across many providers, some of the [[Thousand Points of Light]] that apply to the real-world [[User]], but only those appropriate for the [[Relying Party]] request are enabled by the user.
+*In this wiki the IAP ([[Identifier or Attribute Provider]]) supply a [[Data Category]] only when that category has [[User Consent]]. To get all of those categories that the [[Relying Party]] requires, the request needs to go to a [[User Agent]] that is able to release the data held across many providers, some of the [[Thousand Points of Light]] that apply to the real-world [[User]], but only those appropriate for the [[Relying Party]] request are enabled by the user.
 ==References==