W3C home > Mailing lists > Public > public-credentials@w3.org > April 2021

Re: public key in a verifiable credential

From: Alan Karp <alanhkarp@gmail.com>
Date: Thu, 1 Apr 2021 09:23:39 -0700
Message-ID: <CANpA1Z0DX2z-ffBc3qT9316zc=KMegviW1j5HLa0hwq+J6D4jQ@mail.gmail.com>
To: David Chadwick <D.W.Chadwick@kent.ac.uk>
Cc: "W3C Credentials CG (Public List)" <public-credentials@w3.org>
On Thu, Apr 1, 2021 at 9:09 AM David Chadwick <D.W.Chadwick@kent.ac.uk>

> By  Oauth "client" key you actually mean the subject's (in VC terminology)
> public key. Thus the subject ID is the natural place to put this. Using a
> DID as the subject's ID is either a direct or indirect way of referencing
> the subject's public key. So all VCs do this.

There are many reasons why you would like an authorization certificate to
be issued to a one-off public key.  Using the term "client key" doesn't
preclude that but does get people thinking you are referring to the
client's one and only key.  The same applies to using a DID.  You can
create a DID on the fly, but most people don't think that way.

Alan Karp

Received on Thursday, 1 April 2021 16:24:03 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 1 April 2021 16:24:04 UTC