marius @mariusor@metalhead.club
Public

After much faffing about, I have implemented the dynamic client creation for 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 client to server helper.

[1] datatracker.ietf.org/doc/draft

Logo of the IETF

OAuth Client ID Metadata Document

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.

datatracker.ietf.org · IETF Datatracker

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://metalhead.club/users/mariusor/statuses/115928463387551032 on your instance and quote it. (Note that quoting is not supported in Mastodon.)