Day 2 is in full swing & our WG co-chairs are packing rooms again. Here @josephheenan @kristinayasuda @tplooker and @tlodderstedt review progress on OpenID for VP, including the highly anticipated browser API discussion. Come join this important conversation here or at the WG!

Tobias Looker
@tplookerCTO @mattrglobal

Forever grateful that I get to work with such smart and open-minded people @tlodderstedt @tplooker #openid4vc #ietf116 Kudos to @michael_boyd_ for coining the term #pragmaticenergy and @selfissued for directing the pictures

Finally decided to do something with this domain: jwtf.org/

HTTP Message Signatures has entered evalutation by the IESG. datatracker.ietf.org/doc/dra…

If your interested, check out the current individual draft here github.com/mattrglobal/draft…. Also a link to some slides from a presentation I did on the topic at #iiw last week docs.google.com/presentation…

So why now and why client discovery? I believe we need a simple and common approach documented for the OAuth2 community that enables a wide range of use cases and many of the proposals to date have been more focused on specific applications such as federation or social login.

It pays to note, while the framing of this proposal may be unique, the concept is not. OpenID federation has automatic registration and IndieAuth has documented a similar mechanism. Also if you look hard enough similar thinking can be traced back to OpenID 2 and SAML.

So what if we viewed this problem a little differently? What if the client identified to the AS using an ID that is, assigned and controlled by it, globally unique and can be used to resolve to its metadata, a URL. Enter the concept "client discovery".

For example with DCR, clients are forced to obtain and manage a client ID per AS, and in some cases the client may need to register multiple times because of local storage limitations (e.g SPA's type clients) leading to dead registrations on the AS.

The challenge to solve as ecosystems scale is how these parties can interact with minimal friction while retaining the core properties of the protocol. Dynamic Client Registration (DCR) was introduced to try and solve some of this, however it comes with its own set of challenges.

Conventional OAuth2 requires the client to register with the authorization server (AS) in order to be able to interact. This model is powerful but limiting, especially as ecosystems scale to involve many clients and AS's.

Trying something new here, let's see how it pans out 🤷♂️ OAuth2 Client Discovery, what is it? A proposal to the OAuth2 community. A thread 🧵

intensive and heated discussion on metedata discovery aka federation #iiw

EU eIDAS v2 added #openid4vcs in the short list. #iiw

Super approachable session on a complex topic, great work @timcappalli #passkey #iiw

Awesome turn out for the OpenID for Verifiable Credentials 101 session this morning! @openid #iiw @tlodderstedt @kristinayasuda @OliverTerbu










