[GNAP] Client discovery

"Varley, Mike" <mike.varley@avast.com> Wed, 10 August 2022 13:01 UTC

MIME-Version: 1.0
References: <CAM_o2M-31hfOLdV+pXz1FdywFYyM9UWLoxOfxO+U1uTK_+BTOg@mail.gmail.com>
In-Reply-To: <CAM_o2M-31hfOLdV+pXz1FdywFYyM9UWLoxOfxO+U1uTK_+BTOg@mail.gmail.com>
From: "Varley, Mike" <mike.varley@avast.com>
Date: Wed, 10 Aug 2022 09:01:37 -0400
Message-ID: <CAM_o2M95-JAG+fSer8THLQFK5cYi5v7Tpd+p_xs648CHg+F-9A@mail.gmail.com>
To: txauth@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/bP3RJngHOVM3nfCgYOEOuxlbdyg>
Subject: [GNAP] Client discovery
Precedence: list

Resending, apologies if you received this twice.
(I forgot to register my new email address with the list - hopefully
this goes through!)

-------

There is a proposal in the OpenID Connect group on client discovery:
https://bitbucket.org/openid/connect/issues/1589/proposal-for-supporting-client-discovery

As part of the initial request, there is a mechanism whereby a
client_id can be used to resolve to client-meta data for the AS to
make a determination as to whether the client is qualified to
communicate with the AS.

For GNAP, this seems like something that may fit in with Identifying
the Client Instance; Section 2.3.1 Identifying Client by Reference
section.

I realise it may be a bit late for changes, but would the group be
open to adding normative text on how an AS should handle client
references that are URLs?

I could submit a PR - but there may be a lot of details to cover here
so it may be more suitable as an extension?

Thoughts?

MV

[GNAP] Client discovery Varley, Mike
Re: [GNAP] Client discovery Fabien Imbault
Re: [GNAP] Client discovery Varley, Mike
Re: [GNAP] Client discovery Fabien Imbault
Re: [GNAP] Client discovery Tobias Looker
Re: [GNAP] Client discovery Fabien Imbault