Proposal: OAuth Scopes · bluesky-social atproto · Discussion #3655

Note: a more complete proposal was published in July 2025: https://github.com/bluesky-social/proposals/tree/main/0011-auth-scopes We’re continuing work on rolling OAuth out to the atproto network. ...

Oauth scopes vs record permissions

i hope this is an alright place to put this, but it was just a thought i had inspired by this tweet even with oauth scopes, i think that interoperability between applications is a tough problem because i have to fully trust every oauth client that i use with access to record namespaces. so if i have existing bluesky records, and then i want to use a different application which wants to be able to create and delete bluesky records, either i can’t use bluesky features in that application, or i ne...

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...

Scope Builder - AT Protocol Docs - AT Protocol

Interactive tool for building OAuth scope strings and permission sets.

PDS: review existing oauth scopes via connected apps list · Issue #4838 · bluesky-social/atproto

Scenario I want to stay on top of which apps are messing with what in my PDS. To do so, it's not enough to just make a granular Goldilocks decision once per app. (The more apps I use, the fewer...

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.

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...

tijs/atproto-oauth

Framework-agnostic OAuth integration for AT Protocol (Bluesky) applications

Updated Auth Scopes Proposal · bluesky-social atproto · Discussion #4013

This is a discussion thread for the July 2025 Auth Scopes proposal