Add openid4vp: as a safelisted scheme for protocol registration handling · Issue #11552 · whatwg/html

Pocket ID | Easy Self-Hosted OIDC Provider with Passkeys

Pocket ID is an easy-to-use, self-hosted OpenID Connect Certified™ and OAuth 2.0 provider. Users sign in to your apps with passkeys instead of passwords.

Digital Credentials · Issue #1003 · mozilla/standards-positions

Request for Mozilla Position on an Emerging Web Specification Specification title: Digital Credentials Specification or proposal URL (if available): https://wicg.github.io/digital-identities/ Expla...

Proposal: OAuth-based account creation · bluesky-social atproto · Discussion #4587

We recently added to the reference PDS (and underlying OAuth Provider) implementation support for Initiating User Registration via OpenID Connect 1.0, however, what I wasn't aware of when I add...

OpenID: The Web's Most Successful Failure | WIRED

archived 12 Sep 2024 15:19:57 UTC

Introducing World ID 4.0 - Request for Comments

The new World ID 4.0 upgrade introduces account abstraction with multi-key support, transforming a World ID from a single secret into an abstract record in a public registry. This increases protocol resilience by allowing the introduction of multiple key support, portability, recovery and improved privacy.

@atproto/oauth-provider - AT Protocol

OAuth 2.0 and OpenID Connect authorization server for AT Protocol

OAuth Client ID Metadata Document

This specification defines a mechanism through which an OAuth client can identify itself to authorization servers, without prior dynamic client registration or other existing registration. This is through the usage of a URL as a client_id in an OAuth flow, where the URL refers to a document containing the necessary client metadata, enabling the authorization server to fetch the metadata about the client as needed.

OAuth Client ID Metadata Document

This specification defines a mechanism through which an OAuth client can identify itself to authorization servers, without prior dynamic client registration or other existing registration. This is through the usage of a URL as a client_id in an OAuth flow, where the URL refers to a document containing the necessary client metadata, enabling the authorization server to fetch the metadata about the client as needed.

google/longfellow-zk

Implementation of the Google Zero-Knowledge library for Identity Protocols.

Let's fix OAuth in MCP

Update: The changes described in this blog post have been incorporated into the 2025-06-18 version of the MCP spec!

OAuth for AT Protocol | Bluesky

We are very happy to release the initial specification of OAuth for AT Protocol! This is expected to be the primary authentication and authorization system between atproto client apps and PDS instances going forward, replacing the current flow using App Passwords and createSession over time.

OAuth scopes (#3806) · bluesky-social/atproto@1899b1f

* style: prefix `id` and `uri` with `request` where applicable * Dynamically validate OAuth scopes * Allow configuring trusted OAuth clients * Improve client validation * Rework authorization t...