18684 lines
90 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!doctype html>
<!--
Minimal Mistakes Jekyll Theme 4.24.0 by Michael Rose
Copyright 2013-2020 Michael Rose - mademistakes.com | @mmistakes
Free for personal and commercial use under the MIT license
https://github.com/mmistakes/minimal-mistakes/blob/master/LICENSE
-->
<html lang="en" class="no-js">
<head>
<meta charset="utf-8">
<!-- begin _includes/seo.html --><title>WebAuthN - W3C | Verifiable Credentials and Self Sovereign Identity Web Directory</title>
<meta name="description" content="Allows users to register and authenticate on websites or mobile apps using an “authenticator” instead of a password.">
<meta name="author" content="DIDecentral">
<meta property="article:author" content="DIDecentral">
<meta property="og:type" content="article">
<meta property="og:locale" content="en_US">
<meta property="og:site_name" content="Verifiable Credentials and Self Sovereign Identity Web Directory">
<meta property="og:title" content="WebAuthN - W3C">
<meta property="og:url" content="https://decentralized-id.com/web-standards/w3c/webauthn/">
<meta property="og:description" content="Allows users to register and authenticate on websites or mobile apps using an “authenticator” instead of a password.">
<meta property="og:image" content="https://decentralized-id.com/images/DID_og.webp">
<meta name="twitter:site" content="@infominer33">
<meta name="twitter:title" content="WebAuthN - W3C">
<meta name="twitter:description" content="Allows users to register and authenticate on websites or mobile apps using an “authenticator” instead of a password.">
<meta name="twitter:url" content="https://decentralized-id.com/web-standards/w3c/webauthn/">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:image" content="https://decentralized-id.com/images/DID_og.webp">
<meta property="article:published_time" content="2020-01-09T00:00:00+13:00">
<meta property="article:modified_time" content="2023-05-19T00:00:00+13:00">
<link rel="canonical" href="https://decentralized-id.com/web-standards/w3c/webauthn/">
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Infominer",
"url": "https://decentralized-id.com/"
}
</script>
<!-- end _includes/seo.html -->
<link href="/feed.xml" type="application/atom+xml" rel="alternate" title="Verifiable Credentials and Self Sovereign Identity Web Directory Feed">
<!-- https://t.co/dKP3o1e -->
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<script>
document.documentElement.className = document.documentElement.className.replace(/\bno-js\b/g, '') + ' js ';
</script>
<!-- For all browsers -->
<link rel="stylesheet" href="/assets/css/main.css">
<link rel="preload" href="https://cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@5/css/all.min.css" as="style" onload="this.onload=null;this.rel='stylesheet'">
<noscript><link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@5/css/all.min.css"></noscript>
<meta name="yandex-verification" content="876ea269be433d62" />
<!-- Favicons -->
<link rel="apple-touch-icon" sizes="180x180" href="https://decentralized-id.com/assets/icons/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="https://decentralized-id.com/assets/icons/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="https://decentralized-id.com/assets/icons/favicon-16x16.png">
<link rel="manifest" href="https://decentralized-id.com/assets/icons/site.webmanifest">
<link rel="mask-icon" href="https://decentralized-id.com/assets/icons/safari-pinned-tab.svg" color="#eeeeef">
<link rel="shortcut icon" href="https://decentralized-id.com/assets/icons/favicon.ico">
<meta name="msapplication-TileColor" content="#eeeeef">
<meta name="msapplication-config" content="https://decentralized-id.com/assets/icons/browserconfig.xml">
<meta name="theme-color" content="#eeeeef">
<!-- start custom head snippets -->
<!-- insert favicons. use https://realfavicongenerator.net/ -->
<!-- end custom head snippets -->
</head>
<body class="layout--standards wide">
<nav class="skip-links">
<ul>
<li><a href="#site-nav" class="screen-reader-shortcut">Skip to primary navigation</a></li>
<li><a href="#main" class="screen-reader-shortcut">Skip to content</a></li>
<li><a href="#footer" class="screen-reader-shortcut">Skip to footer</a></li>
</ul>
</nav>
<div class="masthead">
<div class="masthead__inner-wrap">
<div class="masthead__menu">
<nav id="site-nav" class="greedy-nav">
<a class="site-logo" href="/"><img src="/images/DID.webp" alt="Decentralized Identity"></a>
<a class="site-title" href="/">
Decentralized Identity
</a>
<ul class="visible-links"><li class="masthead__menu-item">
<a href="/introduction/">Introduction</a>
</li><li class="masthead__menu-item">
<a href="/ecosystem/">Ecosystem</a>
</li><li class="masthead__menu-item">
<a href="/posts/">New</a>
</li><li class="masthead__menu-item">
<a href="/recent/">Updated</a>
</li><li class="masthead__menu-item">
<a href="/categories/">Categories</a>
</li><li class="masthead__menu-item">
<a href="/about/">Welcome</a>
</li><li class="masthead__menu-item">
<a href="/aim/">Aim</a>
</li></ul>
<button class="greedy-nav__toggle hidden" type="button">
<span class="visually-hidden">Toggle menu</span>
<div class="navicon"></div>
</button>
<ul class="hidden-links hidden"></ul>
</nav>
</div>
</div>
</div>
<div class="initial-content">
<div id="main" role="main">
<div class="sidebar sticky">
<img src="/images/the-world-map-from-a-binary-code.webp"
alt="Binary Globe by GDj">
<h3>Identity Decentralized</h3>
<nav class="nav__list">
<input id="ac-toc" name="accordion-toc" type="checkbox" />
<label for="ac-toc">Toggle menu</label>
<ul class="nav__items">
<li>
<a href="/"><span class="nav__sub-title">Home</span></a>
<ul>
<li><a href="/history/">• Resources & Pre-History</a></li>
<li><a href="/history/2000-2009/">• 2000-2009</a></li>
<li><a href="/history/2010-2014/">• 2010-2014</a></li>
<li><a href="/history/2015-2019/">• 2015-2019</a></li>
</ul>
</li>
<li>
<a href="/categories/#companies"><span class="nav__sub-title">New Pages New Structure</span></a>
<ul>
<li><a href="/companies/ValidatedID/">• ValidatedID</a></li>
<li><a href="/companies/ValidatedID/">• SpruceID</a></li>
<li><a href="/companies/Spherity/">• Spherity</a></li>
<li><a href="/companies/MyDEX/">• MyDEX</a></li>
<li><a href="/companies/Mattereum/">• Mattereum</a></li>
<li><a href="/companies/MagicLabs/">• Magic Labs</a></li>
<li><a href="/companies/Lissi/">• Lissi</a></li>
<li><a href="/companies/Indicio/">• Indicio</a></li>
<li><a href="/companies/IDramp/">• IDRamp</a></li>
<li><a href="/companies/GlobalID/">• GlobalID</a></li>
<li><a href="/companies/Gataca/">• Gataca</a></li>
</ul>
</li>
<li>
<span class="nav__sub-title">Literature</span>
<ul>
<li><a href="https://identosphere.net/">• Identosphere Blog Catcher</a></li>
<li><a href="https://newsletter.identosphere.net/">• Identosphere Newsletter</a></li>
<li><a href="/literature/self-sovereign-identity/">• SSI Literature</a></li>
<li><a href="/workshops/internet-identity-workshop/">• IIW Session Topics</a></li>
<li><a href="/workshops/rebooting-web-of-trust/">• RWoT Papers Index</a></li>
</ul>
</li>
<li>
<a href="/web-standards/"><span class="nav__sub-title">Web Standards</span></a>
<ul>
<li><a href="/web-standards/w3c/">• W3C</a></li>
<li><a href="/web-standards/w3c/wg/vc/verifiable-credentials/">• Verifiable Credentials</a></li>
<li><a href="/web-standards/linked-data/JSON-LD/">• JSON-LD</a></li>
<li><a href="/web-standards/gs1/">• GS1</a></li>
</ul>
</li>
<li>
<span class="nav__sub-title">Regulation</span>
<ul>
<li><a href="/government/europe/regulation/eidas/">• eIDAS</a></li>
<li><a href="/government/europe/regulation/gdpr/">• GDPR</a></li>
</ul>
</li>
<li>
<a href="/organizations/"><span class="nav__sub-title">Organizations</span></a>
<ul>
<li><a href="/organizations/decentralized-identity-foundation/">• Identity Foundation</a></li>
<li><a href="/organizations/mydata/">• My Data</a></li>
<li><a href="/blockchain/hyperledger/">• Hyperledger Foundation</a></li>
<li><a href="/organizations/sovrin-foundation/">• Sovrin Foundation</a></li>
<li><a href="/organizations/ssi-meetup/">• SSI Meetup</a></li>
<li><a href="/organizations/women-in-identity/">• Women in Identity</a></li>
</ul>
</li>
<li>
<span class="nav__sub-title">Infominer</span>
<ul>
<li><a href="https://infominer.xyz/">• InfoHub</a></li>
<li><a href="https://identosphere.net/">• Identosphere Newsletter</a></li>
<li><a href="https://identosphere.net/">• Identosphere BlogCatcher</a></li>
<li><a href="https://bitcoinfo.github.io/history/">• Bitcoin Histories</a></li>
<li><a href="https://sourcecrypto.github.io/decentralized-web/">• Decentralized Web Histories</a></li>
<li><a href="https://sourcecrypto.github.io">• Source⧉Crypto</a></li>
</ul>
</li>
</ul>
</nav>
</div>
<article class="page h-entry" itemscope itemtype="https://schema.org/CreativeWork">
<meta itemprop="headline" content="WebAuthN - W3C">
<meta itemprop="description" content="The Web Authentication Working Group will develop recommendation-track specifications defining an API, as well as signature and attestation formats which provide an asymmetric cryptography-based foundation for authentication of users to Web Applications.Overall goals include obviating the use of shared secrets, i.e. passwords, as authentication credentials, facilitating multi-factor authentication support as well as hardware-based key storage while respecting the Same Origin Policy (SOP) by default and allowing for explicit, constrained SOP relaxation.">
<meta itemprop="datePublished" content="2020-01-09T00:00:00+13:00">
<meta itemprop="dateModified" content="2023-05-19T00:00:00+13:00">
<div class="page__inner-wrap">
<header>
<h1 id="page-title" class="page__title p-name" itemprop="headline">
<a href="https://decentralized-id.com/web-standards/w3c/webauthn/" class="u-url" itemprop="url">WebAuthN - W3C
</a>
</h1>
<p class="page__meta">
<span class="page__meta-readtime">
<i class="far fa-clock" aria-hidden="true"></i>
less than 1 minute read
</span>
</p>
</header>
<section class="page__content e-content" itemprop="text">
<aside class="sidebar__right ">
<nav class="toc">
<header><h4 class="nav__title"><i class="fas fa-link"></i> Contents</h4></header>
<ul class="toc__menu"><li><a href="#Main">Main</a></li><li><a href="#FIDO Alliance">FIDO Alliance</a></li><li><a href="#Working Group">Working Group</a></li></ul>
</nav>
</aside>
<h2 id="Main">Main</h2><ul>
<li><a href="https://techcommunity.microsoft.com/t5/identity-standards-blog/why-webauthn-will-change-the-world/ba-p/482286">Why WebAuthn will change the world</a>
<strong>From</strong>: Microsoft
<strong>By</strong>:
Pamela Dingle
<strong>Type: </strong>Post
<strong>Date:</strong> 2019-04-19
</li>
<blockquote><p>A little over a month ago, W3C WebAuthn became a real internet specification. Most of you dont know what WebAuthn is yet, but many of you will feel the impact in short order. In fact, I will go so far as to say that WebAuthn may change how we all authenticate to the resources we use every day. <br /><br />We live in a world where the best parts of our individual local hardware and software collection are rarely leveraged to make cloud security decisions. This is because there has never been a vendor-agnostic and privacy-preserving way for cloud resources to interact with individual hardware configurations in any generic way. Until now! <br /><br />With WebAuthn, any web entity can call a simple Javascript API and ask for a cryptographically secure credential. What happens next is pretty cool the worlds browsers have worked with the worlds operating system makers and the worlds hardware manufacturers, so that when a website asks for a credential, the browsers work with the underlying platform to securely locate compliant local hardware and talk to it!</p>
</blockquote>
<li><a href="https://www.zdnet.com/article/w3c-finalizes-web-authentication-webauthn-standard/">W3C finalizes Web Authentication (WebAuthn) standard - ZDNet</a>
<strong>From</strong>: ZDNet
<strong>Type: </strong>Post
<strong>Date:</strong> 2019-03-04
</li>
<blockquote><p>WebAuthn allows users to register and authenticate on websites or mobile apps using an “authenticator” instead of a password.<br /><br />The “authenticator” can be a hardware security key that the user has connected to his computer or a biometric ID that can be acquired from the PC or smartphones sensors such as fingerprints, face scans, iris scans, and others.</p>
</blockquote>
<li><a href="https://techcommunity.microsoft.com/t5/Identity-Standards-Blog/All-about-FIDO2-CTAP2-and-WebAuthn/ba-p/288910">All about FIDO2, CTAP2 and WebAuthn</a>
<strong>From</strong>: Microsoft
<strong>Type: </strong>Post
<strong>Date:</strong> 2018-11-20
</li>
<blockquote><p>This is a great week to be working in Identity Standards, as we at Microsoft celebrate the release of our first ever WebAuthn Relying Party. This one relying party enables standards-based passwordless authentication at Xbox, Skype, Outlook.com and more. But what are the actual pieces of the puzzle and how do they fit? Read on for the big picture of how the W3C WebAuthn and FIDO2 CTAP2 specifications interact. We will start with the industry standards perspective, and then at the end we will summarize how Microsoft implements the various roles. <br /><br />To understand how FIDO2 authenticators work, you need knowledge of two specifications in two different standards bodies. The WebAuthentication (aka WebAuthn) spec lives at W3C (where the browser makers meet) while the Client-to-Authenticator (aka CTAP2) spec lives at the FIDO Alliance (where hardware and platform folks have joined to solve the problem of Fast IDentity Online).</p>
</blockquote>
<ul><li><img src="https://techcommunity.microsoft.com/t5/image/serverpage/image-id/60283iDDAE6B0B53A24427/image-size/original?v=v2&px=-1"/></li></ul>
<li><a href="https://techcommunity.microsoft.com/t5/identity-standards-blog/to-understand-webauthn-read-credman/ba-p/339652">To Understand WebAuthn, Read CredMan</a>
<strong>From</strong>: Microsoft
<strong>Type: </strong>Post
<strong>Date:</strong> 2019-02-15
</li>
<blockquote><p>The holidays are well and truly over, time to get serious - now is the perfect time to read specifications! If you are planning to read the WebAuthn specification, you can ease into the terminology in a simple way - take a cruise through the W3C Credential Management (aka CredMan) specification first. CredMan sets up the object model for the Credential object model that WebAuthns PublicKeyCredential extends. This post will be an overview of the CredMan spec, geared for folks who want to call the API as clients, not for those few and proud who are tasked with implementation of the API within a user agent.</p>
</blockquote>
<ul><li><img src="https://techcommunity.microsoft.com/t5/image/serverpage/image-id/78172i3FDF4848680EABE1/image-size/original?v=v2&px=-1"/></li></ul>
<li><a href="https://github.blog/2019-08-21-github-supports-webauthn-for-security-keys/">GitHub supports Web Authentication (WebAuthn) for security keys</a>
<strong>From</strong>: GitHub
<strong>By</strong>:
Lucas Garron
<strong>Type: </strong>Post
<strong>Date:</strong> 2019-08-21
</li>
<blockquote><p>GitHub now supports Web Authentication (WebAuthn) for security keys—the new standard for secure authentication on the web. Starting today, you can use security keys for two-factor authentication on GitHub with even more browsers and devices. And, since many browsers are actively working on WebAuthn features, were excited about the potential for strong and easy-to-use authentication options for the entire GitHub community in the future.</p>
</blockquote>
<ul><li><img src="https://github.blog/wp-content/uploads/2019/08/Screen-Shot-2019-08-21-at-11.34.02-copy.png?fit=2400%2C1260"/></li></ul>
<li><a href="https://slides.com/fidoalliance/webauthn-overview">WebAuthn Workshop</a>
<strong>From</strong>: Fido Alliance
<strong>Type: </strong>Presentation
<strong>Date:</strong> 2018-06-07
</li>
<ul><li><img src="https://media.slid.es/thumbnails/0d31fdc30b303d4443a65dd550767eee/thumb.jpg?1538300008"/></li></ul>
<li><a href="https://github.com/herrjemand/awesome-webauthn">WebAuthn Awesome Awesome</a>
<strong>By</strong>:
Ackermann Yuri
<strong>Type: </strong>List
<strong>Date:</strong> 2023-04-06
</li>
<blockquote><p>A curated list of awesome WebAuthn/FIDO2 resources</p>
</blockquote>
<li><a href="https://webauthn.guide">Guide to Web Authentication</a>
<strong>From</strong>: WebAuthN Guide
<strong>Type: </strong>Page
</li>
<blockquote><p>Passwords have an ever-growing list of problems associated with them, both for users and developers. Users have to worry about passwords being stolen by phishing tools, or their passwords being leaked online if websites they have accounts with are compromised. They have to worry about creating and remembering passwords without dedicated password management tools. Developers have to worry about all the complications of passing passwords through systems and safely storing them in databases.</p>
</blockquote>
<li><a href="https://webauthn.me">Web Authentication (WebAuthn) Credential and Login Demo</a>
<strong>From</strong>: Auth0
<strong>Type: </strong>Page
</li>
<blockquote><p>Web Authentication is a W3C recommendation for defining an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users.<br /><br />Web Authentication works hand in hand with other industry standards such as Credential Management Level 1 and FIDO 2.0 Client to Authenticator Protocol 2.<br /><br />Auth0 allows you to quickly setup Multi-Factor Authentication with WebAuthn</p>
</blockquote>
</ul>
<h2 id="FIDO Alliance">FIDO Alliance</h2><ul>
<li><a href="https://fidoalliance.org/fido2/">FIDO2: WebAuthn & CTAP</a>
<strong>From</strong>: FIDO Alliance
<strong>Type: </strong>Page
</li>
<blockquote><p>The FIDO Alliance developed FIDO Authentication standards based on public key cryptography for authentication that is more secure than passwords and SMS OTPs, simpler for consumers to use, and easier for service providers to deploy and manage. FIDO Authentication enables password-only logins to be replaced with secure and fast login experiences across websites and apps.</p>
</blockquote>
<li><a href="https://fidoalliance.org/fido2/fido2-web-authentication-webauthn/">FIDO2: Web Authentication (WebAuthn)</a>
<strong>From</strong>: FIDO Alliance
<strong>Type: </strong>Page
</li>
<blockquote><p>Web Authentication (WebAuthn), a core component of FIDO Alliances FIDO2 set of specifications, is a web-based API that allows websites to update their login pages to add FIDO-based authentication on supported browsers and platforms. FIDO2 enables users to leverage common devices to easily authenticate to online services in both mobile and desktop environments.</p>
</blockquote>
</ul>
<h2 id="Working Group">Working Group</h2><ul>
<li><a href="https://www.w3.org/Webauthn/">Web Authentication Working Group</a>
<strong>From</strong>: WebAuthNWG
<strong>Related</strong>: W3C
<strong>Type: </strong>Working group
<strong>Established:</strong> 2016-02-08
</li>
<blockquote><p>The mission of the Web Authentication Working Group, in the Security Activity is to define a client-side API providing strong authentication functionality to Web Applications.</p>
</blockquote>
<li><a href="https://w3c.github.io/webauthn/">Web Authentication: An API for accessing Public Key Credentials</a>
<strong>From</strong>: WebAuthNWG
<strong>Related</strong>: W3C
<strong>Type: </strong>Specification
<strong>Date:</strong> 2023-05-17
</li>
<blockquote><p>This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. Conceptually, one or more public key credentials, each scoped to a given WebAuthn Relying Party, are created by and bound to authenticators as requested by the web application. The user agent mediates access to authenticators and their public key credentials in order to preserve user privacy. Authenticators are responsible for ensuring that no operation is performed without user consent. Authenticators provide cryptographic proof of their properties to Relying Parties via attestation. This specification also describes the functional model for WebAuthn conformant authenticators, including their signature and attestation functionality.</p>
</blockquote>
<ul><li><img src="https://w3c.github.io/webauthn/images/webauthn-registration-flow-01.svg"/></li></ul>
<li><a href="https://www.w3.org/2019/10/webauthn-wg-charter.html">Web Authentication Working Group Charter</a>
<strong>From</strong>: WebAuthNWG
<strong>By</strong>:
Samuel Weiler
<strong>Type: </strong>Post
<strong>Date:</strong> 2019-10-15
</li>
<blockquote><p>The Web Authentication Working Group will develop recommendation-track specifications defining an API, as well as signature and attestation formats which provide an asymmetric cryptography-based foundation for authentication of users to Web Applications.<br /><br />Overall goals include obviating the use of shared secrets, i.e. passwords, as authentication credentials, facilitating multi-factor authentication support as well as hardware-based key storage while respecting the Same Origin Policy (SOP) by default and allowing for explicit, constrained SOP relaxation.</p>
</blockquote>
</ul>
</ul>
</section>
<footer class="page__meta">
<h4 class="page__meta-title">Meta</h4>
<p class="page__taxonomy">
<strong><i class="fas fa-fw fa-tags" aria-hidden="true"></i> Tags </strong>
<span itemprop="keywords">
<a href="/tags/#fido" class="page__taxonomy-item p-category" rel="tag">FIDO</a><span class="sep">, </span>
<a href="/tags/#microsoft" class="page__taxonomy-item p-category" rel="tag">Microsoft</a><span class="sep">, </span>
<a href="/tags/#stranger-labs" class="page__taxonomy-item p-category" rel="tag">Stranger Labs</a><span class="sep">, </span>
<a href="/tags/#w3c" class="page__taxonomy-item p-category" rel="tag">W3C</a><span class="sep">, </span>
<a href="/tags/#webauthn" class="page__taxonomy-item p-category" rel="tag">WebAuthN</a>
</span>
</p>
<p class="page__taxonomy">
<strong><i class="fas fa-fw fa-folder-open" aria-hidden="true"></i> Categories: </strong>
<span itemprop="keywords">
<a href="/categories/#related-standards" class="page__taxonomy-item p-category" rel="tag">Related Standards</a>
</span>
</p>
<p class="page__date"><strong><i class="fas fa-fw fa-calendar-alt" aria-hidden="true"></i> Updated:</strong> <time class="dt-published" datetime="2023-05-19">May 19, 2023</time></p>
</footer>
<section class="page__share">
<h3 class="page__share-title">Share on</h3>
<a href="https://twitter.com/intent/tweet?via=infominer33&text=WebAuthN+-+W3C%20https%3A%2F%2Fdecentralized-id.com%2Fweb-standards%2Fw3c%2Fwebauthn%2F" class="btn btn--twitter" onclick="window.open(this.href, 'window', 'left=20,top=20,width=500,height=500,toolbar=1,resizable=0'); return false;" title="Share on Twitter"><i class="fab fa-fw fa-twitter" aria-hidden="true"></i><span> Twitter</span></a>
<a href="https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fdecentralized-id.com%2Fweb-standards%2Fw3c%2Fwebauthn%2F" class="btn btn--facebook" onclick="window.open(this.href, 'window', 'left=20,top=20,width=500,height=500,toolbar=1,resizable=0'); return false;" title="Share on Facebook"><i class="fab fa-fw fa-facebook" aria-hidden="true"></i><span> Facebook</span></a>
<a href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdecentralized-id.com%2Fweb-standards%2Fw3c%2Fwebauthn%2F" class="btn btn--linkedin" onclick="window.open(this.href, 'window', 'left=20,top=20,width=500,height=500,toolbar=1,resizable=0'); return false;" title="Share on LinkedIn"><i class="fab fa-fw fa-linkedin" aria-hidden="true"></i><span> LinkedIn</span></a>
<a href="https://www.reddit.com/submit?url=https%3A%2F%2Fdecentralized-id.com%2Fweb-standards%2Fw3c%2Fwebauthn%2F&title=WebAuthN+-+W3C" class="btn btn--reddit" title="Share on Reddit"><i class="fab fa-fw fa-reddit" aria-hidden="true"></i><span> Reddit</span></a>
</section>
<nav class="pagination">
<a href="/decentralized-web/scuttlebot/" class="pagination--pager" title="Secure Scuttlebutt
">Previous</a>
<a href="/about/" class="pagination--pager" title="Welcome to Decentralized-ID.com!
">Next</a>
</nav>
</div>
<div class="page__comments">
<section id="static-comments">
</section>
</div>
</article>
<div class="page__related">
<h2 class="page__related-title">See Also</h2>
<div class="grid__wrapper">
<div class="grid__item">
<article class="archive__item" itemscope itemtype="https://schema.org/CreativeWork">
<div class="archive__item-teaser">
<img src="/images/did-square.webp" alt="">
</div>
<br><strong><a href="/ecosystem/" rel="permalink">Ecosystem Overview
</a></strong>
<p class="archive__item-excerpt" itemprop="description">This page includes a breakdown of the Web Standards, Protocols,Open Source Projects, Organizations, Companies, Regions, Government and Policy surrounding Verifiable Credentials and Self Sovereign Identity.
</p>
<p class="page__meta"><strong>Updated:</strong> 2024-02-26 <i class="far fa-clock" aria-hidden="true"></i>
4 minute read
</p>
<small><strong>Tags:</strong></small>
</article>
</div>
<div class="grid__item">
<article class="archive__item" itemscope itemtype="https://schema.org/CreativeWork">
<div class="archive__item-teaser">
<img src="/images/Verifiable-Credentials-Flavors-Explained_jsonld-lds-teaser.webp" alt="">
</div>
<br><strong><a href="/web-standards/w3c/verifiable-credentials/data-integrity-bbs+/" rel="permalink">Verifiable Credentials with JSON-LD and BBS+ Signatures
</a></strong>
<p class="archive__item-excerpt" itemprop="description">BBS signatures were implicitly proposed by Boneh, Boyen, and Shacham (CRYPTO 04) as part of their group signature scheme, and explicitly cast as stand-alone signatures by Camenisch and Lysyanskaya (CRYPTO 04). A provably secure version, called BBS+, was then devised by Au, Susilo, and Mu (SCN ...</p>
<p class="page__meta"><strong>Updated:</strong> 2023-09-29 <i class="far fa-clock" aria-hidden="true"></i>
8 minute read
</p>
<small><strong>Tags:</strong></small>
<div class="tags">BBS</div>
<div class="tags">Data Integrity</div>
<div class="tags">JSON-LD</div>
<div class="tags">Verifiable Credentials</div>
<div class="tags">W3C</div>
</article>
</div>
<div class="grid__item">
<article class="archive__item" itemscope itemtype="https://schema.org/CreativeWork">
<div class="archive__item-teaser">
<img src="/images/Verifiable-Credentials-Flavors-Explained_jwt-teaser.webp" alt="">
</div>
<br><strong><a href="/web-standards/w3c/verifiable-credentials/jose-jwt+cose-cbor/" rel="permalink">Verifiable Credentials with JOSE (JWT) / COSE (CBOR)
</a></strong>
<p class="archive__item-excerpt" itemprop="description">Digital proof mechanisms, a subset of which are digital signatures, are required to ensure the protection of a verifiable credential. Having and validating proofs, which may be dependent on the syntax of the proof (for example, using the JSON Web Signature of a JSON Web Token for proofing a key h...</p>
<p class="page__meta"><strong>Updated:</strong> 2023-09-09 <i class="far fa-clock" aria-hidden="true"></i>
12 minute read
</p>
<small><strong>Tags:</strong></small>
<div class="tags">COSE</div>
<div class="tags">IANA</div>
<div class="tags">JOSE</div>
<div class="tags">JWT</div>
<div class="tags">Verifiable Credentials</div>
<div class="tags">W3C</div>
</article>
</div>
<div class="grid__item">
<article class="archive__item" itemscope itemtype="https://schema.org/CreativeWork">
<div class="archive__item-teaser">
<img src="/images/Verifiable-Credentials-Flavors-Explained_zkp-cl-teaser.webp" alt="">
</div>
<br><strong><a href="/web-standards/w3c/verifiable-credentials/zkp-cl_anoncreds/" rel="permalink">Verifiable Credentials (ZKP-CL) Anoncreds
</a></strong>
<p class="archive__item-excerpt" itemprop="description">This credential format was created specifically to leverage the CL Signatures. JSON-JWT and JSON-LD Signatures each have their own way of representing the meaning of the attributes within a VC. JSON-JWT references an IANA registry and assumes a “closed world” authority model based on that authori...</p>
<p class="page__meta"><strong>Updated:</strong> 2023-09-29 <i class="far fa-clock" aria-hidden="true"></i>
6 minute read
</p>
<small><strong>Tags:</strong></small>
<div class="tags">Anoncreds</div>
<div class="tags">Evernym</div>
<div class="tags">Hyperledger Foundation</div>
<div class="tags">IBM</div>
<div class="tags">IDEMIX</div>
<div class="tags">Sovrin Foundation</div>
<div class="tags">Verifiable Credentials</div>
<div class="tags">W3C</div>
<div class="tags">ZKP-CL</div>
</article>
</div>
</div>
</div>
</div>
</div>
<div id="footer" class="page__footer">
<footer>
<!-- start custom footer snippets -->
<!-- end custom footer snippets -->
<div class="page__footer-follow">
<ul class="social-icons">
<li><strong>Follow:</strong></li>
<li><a href="mailto:nfo@infominer.xyz" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-envelope-square" aria-hidden="true"></i> Email</a></li>
<li><a href="https://decentralized-id.com" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-link" aria-hidden="true"></i> Website</a></li>
<li><a href="https://twitter.com/DecentralizeID" rel="nofollow noopener noreferrer"><i class="fab fa-fw fa-twitter-square" aria-hidden="true"></i> Twitter</a></li>
<li><a href="https://github.com/Decentralized-ID" rel="nofollow noopener noreferrer"><i class="fab fa-fw fa-github" aria-hidden="true"></i> GitHub</a></li>
<li><a href="/feed.xml"><i class="fas fa-fw fa-rss-square" aria-hidden="true"></i> Feed</a></li>
</ul>
</div>
<script data-goatcounter="https://didecentral.goatcounter.com/count" async src="//gc.zgo.at/count.js"></script>
<div class="page__footer-copyright"><a href="https://infominer.xyz">infominer</a><a href="https://creativecommons.org/publicdomain/zero/1.0/">Creative Commons (CC0 1.0) Public Domain</a> • Powered by <a href="https://mademistakes.com/work/minimal-mistakes-jekyll-theme/" rel="nofollow">Minimal Mistakes</a> via <a href="https://web-work.tools/jamstack/github-pages-starter-pack/">Github Pages</a>. ⧉</div>
</footer>
</div>
<script src="/assets/js/main.min.js"></script>
<script src="https://kit.fontawesome.com/4eee35f757.js"></script>
<!-- start custom analytics snippet -->
<!-- end custom analytics snippet -->
</body>
</html>