W3C home > Mailing lists > Public > public-credentials@w3.org > November 2022

Re: Google Browser/FedCM team exploring native APIs for CHAPI

From: Phillip Long <pdlong2@asu.edu>
Date: Tue, 22 Nov 2022 18:44:02 +0000
To: "msporny@digitalbazaar.com" <msporny@digitalbazaar.com>
CC: W3C Credentials CG <public-credentials@w3.org>
Message-ID: <FF89B437-52C3-470F-97A9-C9890ADF7BC0@asu.edu>
Manu: that’s exciting news!  I’m ruing missing the IIW each day as progress like this really comes out of that a the similar RWOT meetings.

I’ll follow up separately, but I’d be very interested in whether this is something that might be worth sharing at an upcoming LER Network meeting?  It’s always good to have examples of possible ways forward, especially when it democratizes the experience of using VCs through integrations with existing widely used and familiar applications. A major segment of the population gets included with moves like this.

Thanks for sharing it.


Phillip D. Long
Orchard - Adaptive Learning Library & LxP Consultant

e: pdlong2@asu.edu<mailto:pdlong2@asu.edu>
LER Network Facilitator
T3 Innovation Network, US Chamber of Commerce Foundation
SNS:  https://www.linkedin.com/in/longpd


On Nov 22, 2022, at 11:50 AM, Manu Sporny <msporny@digitalbazaar.com<mailto:msporny@digitalbazaar.com>> wrote:

Hi all, exciting news (and a request for the CCG Chairs below).

DmitriZ, a handful of IIW attendees, and I had a chat with Sam Goto at
the Internet Identity Workshop last week about providing the
Credential Handler API[1] (CHAPI) with the necessary native browser
API calls to make the experience smoother and browser native.

Sam has kindly written up where we got to at IIW after multiple
meetings and has even implemented a compelling native demo in Chromium
demonstrating how we could achieve open wallet selection! There is an
explanation of how CHAPI works and how it might integrate with FedCM
here (so I won't repeat what's already in the issue in this email, go
here to read more):


The reason this is exciting to the CCG is because there is a very real
interest by a browser vendor in making what we call "open wallet
selection" natively supported in the browser, primarily through CHAPI.
It turns out CHAPI has made many of the same design decisions that
FedCM has made and that there is alignment for a variety of reasons
that have nothing to do with DIDs or VCs.

Sam believes that we can make progress through Google Chrome "canary"
releases (nightly experimental builds that all of us can download and
use with the new functionality built in). If this happens, Digital
Bazaar will commit time and financial resources to using those
experimental native browser APIs and integrating them with the CHAPI
polyfill to upgrade to a native experience if one exists (while
falling back to what's there today in every browser if a native
experience isn't possible).

The next steps are that the Google FedCM team would like to present
this idea to the CCG and would like us to come and present about
CHAPI+FedCM to the FedCM CG.

So, this is a request to the CCG Chairs to put aside time on an
upcoming CCG call to discuss this exciting development with the Google
FedCM team.

-- manu

PS: Huge shout out to DmitriZ for making this happen -- the first 20
times he (and TobiasL) approached me about it, I was like: "pffff,
like that's gonna happen... FedCM cares about existing login flows,
not CHAPI." -- See, SteveC, proof that I don't know what I'm talking
about from time to time! :P


Manu Sporny - https://urldefense.com/v3/__https://www.linkedin.com/in/manusporny/__;!!IKRxdwAv5BmarQ!apbPOdjn1GcDP7boYwwUQWOZ65tAutCkm1XPoBCtYABkezN33ecuVjeLHwxsi8phZnEs0zxKHKvRjcs0kS_lnw$

Founder/CEO - Digital Bazaar, Inc.
News: Digital Bazaar Announces New Case Studies (2021)

Received on Tuesday, 22 November 2022 18:44:21 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 22 November 2022 18:44:23 UTC