5 ms·
Something that should be a bit of a warning flag is that I have two decades of identity-related experience but I still have no idea what DID even is. For refer
by jiggawatts 4y ago
Something that should be a bit of a warning flag is that I have two decades of identity-related experience but I still have no idea what DID even is.
For reference, I've worked with three vendors' implementations of LDAP, several versions of SAML, OAuth, JWT, Okta, Azure Active Directory, etc, etc... I've even deployed Smart Card authentication in the field several times.
I literally have no idea, not a clue what DID is supposed to be in a practical sense, despite having read a significant volume of material on a subject.
Like, okay, it's "identity"... somehow? How? What? Where?
The documentation is impenetrable buzzword-compliant gibberish that makes SAML's documentation look like crystal-clear poetry in comparison.
- A4ET8a8uTh0 4y agoI mean.. as I understand it, you read specs to understand something and as I kept reading it, I have absolutely zero idea what it is or even supposed to be. What is a problem it is trying to solve? I dislike it, because I immediately assume it cannot be good for me.
- topspin 4y agoI found it all pretty simple after looking at it briefly when I first learned about it. A DID URI is a URI with a 'method' and globally unique part: did:method:somegloballyuniqueid. The "did" part is literal; a standardized URI namespace. The method part is some symbol that specifies how the unique id resolves and its representation (JSON, whatever.) The method part is what this story is about; W3C has declined to enshrine a set of methods in the standard. Instead, W3C is delegating to a registry of methods. This registry has already grown to a sizeable number. The idea is that you will apply a DID URI using its method and obtain a DID 'document'. This document has claims, credentials, etc. The DID owner can cryptographically prove the document represents them and relying parties can cryptographical verify claims in the document. The actual workflow is more involved than described here but that's the gist of it. BTW, your list of identity schemes you've had experience with roughly correspond to 'method's, although they aren't 'distributed' in the DID sense.
- WhyNotHugo 4y agoWhat advantages does DID have to something like OpenID? Which is actually decentralised without a central registry.
- fgiveme 4y agoThis is OpenID's privacy policy: https://openid.net/foundation/members/privacy_policy https://openid.net/foundation/members/privacy_policy They will turn your information to the authority when requested. How is that decentralised?
- zaphar 4y agoOpenID is a standard. Openid.net is one provider not the only provider. You are free to use another provider.
- WhyNotHugo 4y agoIt's decentralised because you can pick up any other provider or even host your own (which I did, until OpenID declined from popularity and wasn't accepted anywhere any more).
- CuriousSkeptic 4y agoWhat problem does adding a common “did:” prefix to these identifiers solve over plain old URIs? Or perhaps my question is more general. What problem does this particular common standard address that individually standardised uri-schemes would not?
- makeitdouble 4y agoWhat I get from your explanation: it’s a new way to deal with cases where one proves ownership of something else (but in a more indirect way than exposing or accessing the thing itself) That reminded me of proof of domain ownership, where we point a registrar to an arbitrary field in our domain records to prove it’s ours. Sadly I also don’t have enough imagination to see any practical use for that. It feels like an abstraction above every other systems we have today, except any provider would still need to support both this and the underlying actual protocol…
- tossacctpls 4y agoIdentity is nothing more than a contextual set of memories and attributes.
- WaylonKenning 4y ago(Disclaimer - I work in this space, but these words are my own). My understanding is DIDs are a unique identifier. There's a few methods that can be used regarding the construction of the identifier. It could be a unique key (did:key- https://w3c-ccg.github.io/did-method-key/ https://w3c-ccg.github.io/did-method-key/). It could be using web infrastructure (did:web - https://w3c-ccg.github.io/did-method-web/ https://w3c-ccg.github.io/did-method-web/). It could be using blockchain infrastructure (did:ion). Whatever it is, it becomes an identifier used to receive credentials and send messages to. For example, your digital wallet can have a DID which can be used to store credentials. Your digital wallet can have many DIDs which can be useful to avoid correlation of identities. The credentials (and the identities they represent) themselves are normally bundled into things like Verifiable Credentials (https://www.w3.org/TR/vc-data-model/ https://www.w3.org/TR/vc-data-model/) which have to be issued to something - like a DID.
- jiggawatts 4y agoOn second reading with that background knowledge, the crypto pedigree reveals itself: "decentralized", "distributed", "independently of any centralized registry", "distributed ledger", "non-registry based", etc... It all makes sense now! It's yet another attempt at making Web 3.0 happen. Sigh...
- helpfulclippy 4y agoI'd argue that of those, "distributed ledger" is the only real red-flaggy one -- and even then, only because of its association with blockchain. I think when engineering web technologies, we should hope to find a lot of talk about decentralized, distributed stuff independent of central registries.
- k__ 4y agoYes. There is did:peer: and did:git: don't know what issues some people here have with blockchain scams again.
- EGreg 4y ago
- nl 4y agoIt's a standardized version of Keybase IDs (which can also support non key based identity if you choose)
- kuramitropolis 4y agoPoor Keybase...
- aasasd 4y agoI'm gonna bet just from the requirements list quoted in that post that the implementations are supposed to be blockchains.
- inopinatus 4y agoSpot on. The list at https://www.w3.org/TR/did-spec-registries/#did-methods https://www.w3.org/TR/did-spec-registries/#did-methods tells you everyone who hopes to cash in. Basically it's like a urn, but every sketchy blockchain startup gets their own namespace.
- aasasd 4y agoDo they explain anywhere whether the browser is expected to keep a bunch of multi-gigabyte blockchains on my disk? Or, is it simply that Google, Mozilla and whoever else have to serve verification requests for their users? Or is the whole joke in that none of this is figured out?
- duskwuff 4y agoIf I had to guess, I'd say it's the third one. Given that Mozilla and Google have already publicly objected to this proposal, I don't expect them to implement it. The W3C's word is not the law; no one is obligated to implement every specification they put forth.
- ajvs 4y agoThat's never been a requirement. There exists SPV to verify cryptographic signatures without downloading a blockchain.
- unreal37 4y agoIt's simply a URI standard for crypto signatures. It provides no function except an address to something else. That's why Google is asking for a few "working" integrations to prove the theory. Because someone goes to implement it and figures out the standard is missing something they need critically, they can modify the standard before it becomes a 1.0 standard.
- deleted 4y ago[deleted]
- godmode2019 4y agoThe New Zealand government used DID for their vaccine passport. (Scan to be allowed to enter a building) They removed the core part of the DID standard where they made it expire after 6months. I was told they requested the DID standard as it was needed for future projects.
- capableweb 4y ago> Something that should be a bit of a warning flag is that I have two decades of identity-related experience but I still have no idea what DID even is. I'm not sure this is the "flex" you wanted it to be. A cursory look at the specification gave me a pretty good idea what DID are supposed to be, and for (and I would only say I know enough identity-related stuff in order to implement things in my own services, but not over two decades). The use cases are relatively easy to understand, and there is bunch of implementations in the wild as well. Maybe it would also help by looking at some of the proposed DID methods that are more similar to the approach you're used to. While not centralized, maybe DNS is something you're more familiar with, so you can link it together with existing knowledge? In that case, the specification for the `did:dns` method, using DID together with DNS might be helpful for you: https://danubetech.github.io/did-method-dns/ https://danubetech.github.io/did-method-dns/ What exactly is it you don't understand? Maybe your knowledge about centralized identity management is not helping you in this case, but making it harder to understand.
- dhzhzjsbevs 4y agoReading that DNS spec and all I have to say is that I fucking hope I retire before I have to learn this bullshit.
- high_5 4y agoAs far as I understand it (from skimming through a couple of docs and presentations), DIDs are similar to specs for assertions and/or attributes which are stored in a blockchain which functions as federation metadata datastore and IdP at the same time.
- rufasterisco 4y agoAzure Active Directory is on its way to use DIDs [0] The forces in place here seems to be: - distributed ledgers allow a different (decentralized) paradigm for identity management, where users own their identities and service providers authorize and authenticate them through verifiable credentials - years of blockchains and even more years of web certificates have created processes to handle cryptographic material, that service providers supposedly find more secure than "username and password" to manage the identities issuing the verifiable credentials - in realpolitik, Microsoft (Azure) is expanding in the cloud market by trying to establish a presence in niches (ie: Intel SGX, DIDs) [1] I understand the overall skepticism about blockchain related technologies, but the intrinsic advantages that I see in them are: - (for a service provider) having a tamper-proof log of all the auth changes for an identity - (for a service provider/user) relying on cryptographic signatures allows for a private validation of an identity/claim - (for a user) provided this is not EEE allover again, a greater degree of choices on how to manage your identity I do not have as much experience as you do, so maybe there is some wheel-reinventing that I am not aware of :) 0. https://docs.microsoft.com/en-us/azure/active-directory/verifiable-credentials/how-to-dnsbind https://docs.microsoft.com/en-us/azure/active-directory/veri... 1. https://techcommunity.microsoft.com/t5/identity-standards-blog/ion-we-have-liftoff/ba-p/1441555 https://techcommunity.microsoft.com/t5/identity-standards-bl...
- Communitivity 4y agoThe document "Use Cases and Requirements for Decentralized Identifiers" [1] lays out the following summary of what they are trying to achieve: "1. there should be no central issuing agency; 2. the identifier should be inherently persistent, not requiring the continued operation of an underlying organization; 3. it should be possible to prove control of the identifier cryptographically; 4. it should be possible to discover metadata about the identifier." Additional capabilities got tacked on during discussions, and I think are handled in different specs, such as DID-Messaging, but at it's core the above are the primary requirements. [1] https://www.w3.org/TR/did-use-cases/ https://www.w3.org/TR/did-use-cases/
- k__ 4y agoI'm currently reading Self-Sovereign Identity. Seemed to me that DIDs are a more general version of blockchain addresses. Like, you create a DID from a public key, and everyone who handles DID related stuff can ensure only who controls the related private key is the real owner.
- Spooky23 4y agoConceptually, those solutions that you’ve worked with are about account principals and access management. When you deployed a smartcard, the human identity of the person you were assigning an account principal to was established offline, ultimately linked to proof of birth and residence. Typically your company will validate those credentials to some level for employees. At a minimum, you establish what you need to know for payroll, in other cases you do extensive background investigations. For the public, however, we’re stuck with rudimentary solutions for ID verification (bank/credit accounts, mailing letters, etc) or unreliable and invasive solutions like ID.me. The idea of things like DID and sovereign identity is that the human has agency and can provide or not provide credentials to establish who they are. That could include a verifiable, signed representation of your birth certificate, a professional license or some other credential. Think of it as a new iteration of 90s “web of trust” concepts.
- dboreham 4y agoI have a similar background, and I also know some of the people active in the DID community, and I spent a couple of years trying to get them to explain to me what problem it solved or show me a working application using the tech. My take is that it is a) X.509 re-born with different encoding (JSON-LD vs BER or PEM) and b) a scheme to promote use of certain blockchains for a purpose that blockchains don't suit well.
- WFHRenaissance 4y agoSome reading: https://w3c-ccg.github.io/did-primer/ https://w3c-ccg.github.io/did-primer/