search

aaronpk / draft-parecki-oauth-client-id-metadata-document

Other
1 stars 1 forks source link

Consider minimum set of properties to require for interoperability #15

Open aaronpk opened 2 months ago

aaronpk commented 2 months ago

From Dick's review on the email list: https://mailarchive.ietf.org/arch/msg/oauth/tgHv0MMU8PqyNjwsXIze3BUSn9s/

Along those lines, it may be useful to recommend which of those properties are useful and why. For example, should I have a contact property? I think there should be a minimum to implement so there is interoperability -- otherwise it is hit or miss if it will work. The one bit of client_id_metadata_document_supported will unlikely not be enough to have a successful flow unless there is a MTI.