Self-issued Identifier: Difference between revisions

Revision as of 01:18, 17 June 2020

Wiki Page to track the use of [[1]] in the Identity Ecosystem

With the rise of the W3C program on Decentralized Identifiers, there is a need for the Identity Ecosystem to coordinate with other teams developing this technology.
At the 2020-06-16 meeting of the FIRE WG a liaison effort was approved. That effort is tracked here.

The current work of the Decentralized Identifiers has proceed with little concern for how it might integrate with existing Identity Ecosystems.
Self-issued Identifiers of all types depend on secret values held by the user in portable protected storage, for example a smartphone or WebAuthn key.
If the user's hardware device is stolen or disable, the recover of the user's identifier can be a challenge which could turn into a UX nightmare if not handled well.

@@ Line 6: / Line 6: @@
 ==Problems==
 * The current work of the Decentralized Identifiers has proceed with little concern for how it might integrate with existing [[Identity Ecosystem]]s.
+* Self-issued Identifiers of all types depend on secret values held by the user in portable protected storage, for example a smartphone or WebAuthn key.
+* If the user's hardware device is stolen or disable, the recover of the user's identifier can be a challenge which could turn into a UX nightmare if not handled well.
 ==References==
 * [https://mattrglobal.github.io/oidc-client-bound-assertions-spec/ Client Bound End-User Assertion]