home.social

#cimd — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cimd, aggregated by home.social.

  1. marius @[email protected] ·

    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] datatracker.ietf.org/doc/draft

    #CIMD

    #cimd #activitypub #goactivitypub #oauth2
  2. marius @[email protected] ·

    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] datatracker.ietf.org/doc/draft

    #CIMD

    #cimd #activitypub #goactivitypub #oauth2
  3. marius @[email protected] ·

    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] datatracker.ietf.org/doc/draft

    #CIMD

    #cimd #activitypub #goactivitypub #oauth2
  4. marius @[email protected] ·

    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] datatracker.ietf.org/doc/draft

    #CIMD

    #oauth2 #goactivitypub #activitypub #cimd
  5. marius @[email protected] ·

    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] datatracker.ietf.org/doc/draft

    #CIMD

    #cimd #activitypub #goactivitypub #oauth2