This is still pending decision by the ActivityPub API taskforce, but I'm going to be strongly encouraging us to adopt Client ID Metadata Documents as the way to do client registration for the ActivityPub API.
We likely won't have a final decision within the next two weeks though, as this taskforce has only just been started, but this taskforce is designed to tackle better client to server interactions for ActivityPub. https://github.com/swicg/activitypub-api/tree/main https://github.com/swicg/activitypub-api/tree/main swicg/activitypub-api: ActivityPub API Task Force repository. github.com (@Rifaat: yeah, I accidentally replied to just you earlier, sorry about that) Yours, Emelia Smith > On 22 Sep 2025, at 21:12, Rifaat Shekh-Yusef via Datatracker > <nore...@ietf.org> wrote: > > > Subject: Call for adoption: > draft-parecki-oauth-client-id-metadata-document-03 (Ends 2025-10-06) > > This message starts a 2-week Call for Adoption for this document. > > Abstract: > 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. > > File can be retrieved from: > https://datatracker.ietf.org/doc/draft-parecki-oauth-client-id-metadata-document/ > > Please reply to this message keeping oauth@ietf.org in copy by indicating > whether you support or not the adoption of this draft as a WG document. > Comments to motivate your preference are highly appreciated. > > Authors, and WG participants in general, are reminded of the Intellectual > Property Rights (IPR) disclosure obligations described in BCP 79 [2]. > Appropriate IPR disclosures required for full conformance with the provisions > of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. > Sanctions available for application to violators of IETF IPR Policy can be > found at [3]. > > Thank you. > [1] https://datatracker.ietf.org/doc/bcp78/ > [2] https://datatracker.ietf.org/doc/bcp79/ > [3] https://datatracker.ietf.org/doc/rfc6701/ > > >
_______________________________________________ OAuth mailing list -- oauth@ietf.org To unsubscribe send an email to oauth-le...@ietf.org
