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).
-
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/
-
R AodeRelay shared this topic
-
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/
@thisismissem FYI <img class="not-responsive emoji" src="https://activitypub.space/assets/plugins/nodebb-plugin-emoji/emoji/android/1f604.png?v=9d8ea4df803" title="
" /> -
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 isn't a proposed replacement for DCR, it's just an alternative with different properties that can make it potentially easier to manage at scale in decentralized architectures.
-
Thanks for the clarification.
-
@thisismissem cool, that's why I had the question mark there. In the previous interactions we had about it, you seemed to be quite strongly of the opinion that it's a *much better* alternative, so I assumed "replace" was the intent behind the proposal. Apologies for the misunderstanding.
-
R AodeRelay shared this topic
-
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/
Whilst CIMDs are much better than DCR, CIMDs aren't meant to "replace" DCR, they just provide a different alternative which is a bit more scalable than DCR.
