[OAUTH-WG] OAuth Discovery and what the relying party needs to know

Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Wed, 09 May 2012 17:50 UTC

From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 09 May 2012 20:50:10 +0300
Message-Id: <40FC97F0-B72C-47F4-8206-590BA365997A@gmx.net>
To: "oauth@ietf.org WG" <oauth@ietf.org>, kitten@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: [OAUTH-WG] OAuth Discovery and what the relying party needs to know
Precedence: list

Hi guys, 

at the last IIW we had a discussion about SASL-OAuth and what the SASL server needs to know for discovery. 
The discovery discussions around WebFinger go in the same directions. 

So, I have been wondering whether we have made an informed decision about how the discovery procedure is actually supposed to look like. 

In my view, the relying party (the client) only needs to know who the identity provider (the AS/RS) is. 

Any other views? 

Ciao
Hannes

PS: Please let me know if I should provide more background about the issue.

[OAUTH-WG] OAuth Discovery and what the relying p… Hannes Tschofenig
Re: [OAUTH-WG] OAuth Discovery and what the relyi… John Bradley
Re: [OAUTH-WG] [kitten] OAuth Discovery and what … William Mills
Re: [OAUTH-WG] OAuth Discovery and what the relyi… Hannes Tschofenig
Re: [OAUTH-WG] OAuth Discovery and what the relyi… Klaas Wierenga (kwiereng)
Re: [OAUTH-WG] OAuth Discovery and what the relyi… John Bradley
Re: [OAUTH-WG] [kitten] OAuth Discovery and what … Klaas Wierenga (kwiereng)
Re: [OAUTH-WG] [kitten] OAuth Discovery and what … John Bradley
Re: [OAUTH-WG] [kitten] OAuth Discovery and what … Justin Richer
Re: [OAUTH-WG] [kitten] OAuth Discovery and what … John Bradley
Re: [OAUTH-WG] [kitten] OAuth Discovery and what … SM
Re: [OAUTH-WG] [kitten] OAuth Discovery and what … William Mills