Difference between revisions of "Ion ID"
From MgmtWiki
(→Context) |
(→Context) |
||
| Line 4: | Line 4: | ||
==Context== | ==Context== | ||
Every one knows the problem with identities on the internet. They are not under the control of users, who are extremely interested in their own [[Identity]] and want their own [[Privacy]]. | Every one knows the problem with identities on the internet. They are not under the control of users, who are extremely interested in their own [[Identity]] and want their own [[Privacy]]. | ||
| − | |||
* 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. | * 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. | ||
** In this model it was up to the [[Relying Party]] to establish a link and share a secret with the [[Identifier or Attribute Provider]] in advance of any transactions. | ** In this model it was up to the [[Relying Party]] to establish a link and share a secret with the [[Identifier or Attribute Provider]] in advance of any transactions. | ||
Revision as of 17:00, 27 May 2019
Full Title or Meme
One brand of Decentralized ID (DID) originated by Microsoft.
Context
Every one knows the problem with identities on the internet. They are not under the control of users, who are extremely interested in their own Identity and want their own Privacy.
- The current 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.
- In this model it was up to the Relying Party to establish a link and share a secret with the Identifier or Attribute Provider in advance of any transactions.
- 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.
- The current most common protocol for some sort of a Distributed Identity was OpenID Connect which included Self-issued Identifier, but that feature of OpenID Connect had not been deployed in 2018.
- Microsoft Launches Decentralized Identity Tool on Bitcoin Blockchain[1] which gets better performance at less cost with a technique which is derived from sidechains[2].
Problems
- The big problem is Trust where there are no standards or examples of any trust without a history of trusted behavior.
- Proof of Persistent Identity must be provided. This can be little more than the inclusion of a public key in a block chain, but that cannot provide any Assurance of protection of the Credential.
- Most "pure" Blockchain solutions require more energy or time that is appropriate for a user on a Smart Phone.
Solutions
- Side chains are one solution to the time and energy requirement for a full Blockchain ID solution. Ion ID is one implementation of sidechain.
- A test registration for an Ion ID is here.
References
- ↑ Leigh Cue, Microsoft Launches Decentralized Identity Tool on Bitcoin Blockchain (2019-05-13) Coindesk https://www.coindesk.com/microsoft-launches-decentralized-identity-tool-on-bitcoin-blockchain
- ↑ Daniel Buchner, Toward scalable decentralized identifier systems . Microsoft Blog (2019-05-13) https://techcommunity.microsoft.com/t5/Azure-Active-Directory-Identity/Toward-scalable-decentralized-identifier-systems/ba-p/560168
Other Material
- Decentralized Digital Identities and Blockchain perspective from Microsoft (2018-02-12) From Ankur Patel (@_AnkurPatel) - Principal Program Manager - Microsoft Identity Division.
- Media:Example.ogg
