#cimd — Public Fediverse posts

Currently implementing the Federated Credential Management API
https://w3c-fedid.github.io/FedCM/

Flow and Benefits
https://www.corbado.com/blog/fedcm-federated-credential-management-api

Funny Quote
„Axel Springer (Welt, Bild): German media giant with full FedCM deployment:
- 14x increase in monthly registrations after implementing FedCM“

#FedCM #OAuth #cimd #ActivityPub #fedidev

#ActivityPub

Yesterday I implemented #cimd for the #OAuth and for Client-To-Server SignUp.

Overview https://client.dev/
(click the 'Explore' things for security hints)
because https://github.com/swicg/activitypub-api/issues/1

Technically it is easy, just wanted a nice UI for Client-To-Server so any client can combine it with the webmanifest and servers for menschys, redaktor etc. will support the dark/light things and the properties theme_color and background_color as well …

PS:
For Germans the letter order in the acronym is easy to remember: It is cinnamon for the OAuth sugar [Zimt] ;)

How would a client know that an rfc-8414 (oauth) server supports Client ID Metadata Documents (CIMD)?

#oauth #cimd

After much faffing about, I have implemented the dynamic #OAuth2 client creation for #GoActivityPub services using the Client ID Metadata Document[1] that's been proposed as a replacement(?) for RFC7591 (Dynamic Client Registration Protocol).

The changes are in both the Authorization service and in the BOX #ActivityPub client to server helper.

[1] https://datatracker.ietf.org/doc/draft-ietf-oauth-client-id-metadata-document/

#CIMD