Permission Sets - AT Protocol

Scope Builder - AT Protocol Docs - AT Protocol

Interactive tool for building OAuth scope strings and permission sets.

Permissions - AT Protocol

Auth Permissions for Account Resources

Early Permission Sets · bluesky-social atproto · Discussion #4437

Progress is coming along on "Permission Sets", as part of the atproto OAuth and permission system. As with other parts of the protocol, seeing how this functionality gets implemented for ...

Permission set (#4108) · bluesky-social/atproto@f9dc9aa

* Export constants and type assertion utilities * Add permission set support to oauth provider * improve permission set parsing * Rename `PermissionSet` to `ScopePermissions` * Improve performa...

OAuth - AT Protocol

OAuth for Client/Server Authentication and Authorization

OAuth - AT Protocol

OAuth for Client/Server Authentication and Authorization

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

Scopes - AT Protocol Docs - AT Protocol

Auth for AT Protocol application developers.

OAuth Introduction - AT Protocol

OAuth for AT Protocol application developers.

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.

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