Ion ID - Revision history

Tom: /* Other Material */

2021-11-27T15:00:14Z

‎Other Material

2020-08-22T19:13:06Z

‎Full Title or Meme

2020-08-22T19:12:48Z

‎Full Title or Meme

2020-08-22T19:10:41Z

‎Solutions

2020-08-22T04:05:16Z

‎Context

2019-05-30T01:24:19Z

‎Solutions

2019-05-29T03:20:09Z

‎Solutions

2019-05-29T03:17:17Z

‎Solutions

2019-05-29T00:14:50Z

‎Full Title or Meme

2019-05-29T00:06:25Z

‎Solutions

@@ Line 1: / Line 1: @@
 ==Full Title or Meme==
-The [[Ion ID]] is one brand of [[Decentralized ID]] (DID) originated by Microsoft based on a high performance side tree.<ref name=buchner />
+The [[Ion ID]] is one method of [[Decentralized ID]] (DID) originated by Microsoft based on a high performance side tree.<ref name=buchner />
 ==Context==

@@ Line 1: / Line 1: @@
 ==Full Title or Meme==
-One brand of [[Decentralized ID]] (DID) originated by Microsoft based on a high performance side tree.<ref name=buchner />
+The [[Ion ID]] is one brand of [[Decentralized ID]] (DID) originated by Microsoft based on a high performance side tree.<ref name=buchner />
 ==Context==

@@ Line 19: / Line 19: @@
 *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 [https://didproject.azurewebsites.net/docs/registration.html here]. "In order to complete this registration tutorial, you'll need NPM and NodeJS 8 or later installed on your machine."
 *The file to load for json is on [https://github.com/decentralized-identity/did-auth-jose GitHub]. The following (on 2019-05-23) shows those instructions run from PowerShell in system32, that is definitely not a "best practice".
   PS C:\WINDOWS\system32> npm install @decentralized-identity/did-auth-jose@0.1.12

@@ Line 8: / Line 8: @@
 ** 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<ref>
+* Microsoft Launches Decentralized Identity Tool on [[Bitcoin]] Blockchain<ref>
 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</ref> which gets better performance at less cost with a technique which is derived from sidechains<ref name=buchner>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</ref>.

@@ Line 70: / Line 70: @@
+   ]
+  }
 ==References==

@@ Line 37: / Line 37: @@
   (node:17228) [DEP0011] DeprecationWarning: crypto.Credentials is deprecated. Use tls.SecureContext instead.
   PS C:\WINDOWS\system32>
-* Get a json web token (JWT) to be signed into a signed JWT, or a JWS
+* Get a json web token ([[JWT]]) to be signed into a signed JWT, or a JWS
+  {
    "@context": "https://w3id.org/did/v1",

@@ Line 32: / Line 32: @@
   PS C:\WINDOWS\system32>
 * the file "package.json" is on the gibhub repo. I guess it needed to be copied down first?
 * Generate keys
   PS C:\WINDOWS\system32> node generate-keys.js
@@ Line 38: / Line 37: @@
   (node:17228) [DEP0011] DeprecationWarning: crypto.Credentials is deprecated. Use tls.SecureContext instead.
   PS C:\WINDOWS\system32>
 ==References==