







I think auth should be handled by a middleware. The framework gets signed request headers injected by this middleware, which gives it all the info (userid, role, username, picture) it needs.Sandstorm by @KentonVarda uses this approach: https://t.co/xCk1KRIgcw— Nilesh Trivedi (@nileshtrivedi) February 21, 2023

Identity/AttachedServices - MozillaWiki
We want users to have access to their data, in particular the data that forms their web-browsing context (bookmarks, tabs, web apps, passwords, etc.) from all of their devices. This data should be tied to their identity, so that logging into a device is sufficient to connect to all the services the user has previously set up, whether those services are provided by Mozilla or third parties. These are Identity-Attached Services, which, as a whole, we're code-naming PICL (Profile In the Cloud).
Ask HN: What's the recommended method of adding authentication to a REST API? | Hacker News
The short answer is: don't overthink it. Do the simplest thing that will work: use 16+ byte random keys read from /dev/urandom and stored in a database. The cool-kid name for this is "bearer tokens".

OAuth Patterns - AT Protocol Docs - AT Protocol
Auth for AT Protocol application developers.

OAuth Patterns - AT Protocol Docs - AT Protocol
Auth for AT Protocol application developers.


Authenticated Transfer: Architecture Overview
Authenticated Transfer (AT) is a collection of protocol components that together provide a generic framework for interoperable social web applications, using global aggregations of interlinked, self-certifying data records. This informational document provides an overview of the entire system, as implemented in late 2025. Some of those components may be in scope as work for the IETF, while other components may not. Many components are general-purpose and may find use outside of the context of AT. The intent of this document is to provide context for how all the components can fit together for certain use cases.
Cross-App Authentication on AT Protocol
We recently built cross-app authentication between Roomy and OpenMeet using AT Protocol service auth JWTs. The idea came from @erlend.sh (his writeup), @zicklag.dev introduced me to PDS service auth, and @meri.garden contributed reviews. I made the implementation in both apps: A user logs into Roomy, navigates to an OpenMeet event, and is silently authenticated and able to use their account on OpenMeet without a second login. Full technical writeup: Cross-App Authentication on AT Protocol I’m ...

XRPC requests between atproto servers are authenticated using JWTs. There are some inconsistencies in how OAuth permissions, PDS proxy headers, and JWTs all represent the "audience" of these tokens. This proposal gives background and describes a rough solution. Looking for rapid feedback!
proposals/0013-service-auth-refs at main · bluesky-social/proposals
github.com