IETF Logo Mail Archive

[OAUTH-WG] OAuth discovery draft?

"Manger, James H" <James.H.Manger@team.telstra.com> Tue, 22 June 2010 03:02 UTC

Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B5463A67D0 for <oauth@core3.amsl.com>; Mon, 21 Jun 2010 20:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.584
X-Spam-Level: *
X-Spam-Status: No, score=1.584 tagged_above=-999 required=5 tests=[AWL=-0.115, BAYES_50=0.001, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZSM6blxZOg2b for <oauth@core3.amsl.com>; Mon, 21 Jun 2010 20:02:50 -0700 (PDT)
Received: from ipxano.tcif.telstra.com.au (ipxano.tcif.telstra.com.au [203.35.82.200]) by core3.amsl.com (Postfix) with ESMTP id B01613A659B for <oauth@ietf.org>; Mon, 21 Jun 2010 20:02:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,457,1272808800"; d="scan'208";a="6045544"
Received: from unknown (HELO ipcdni.tcif.telstra.com.au) ([10.97.216.212]) by ipoani.tcif.telstra.com.au with ESMTP; 22 Jun 2010 13:02:54 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,6020"; a="3589561"
Received: from wsmsg3755.srv.dir.telstra.com ([172.49.40.196]) by ipcdni.tcif.telstra.com.au with ESMTP; 22 Jun 2010 13:02:56 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3755.srv.dir.telstra.com ([172.49.40.196]) with mapi; Tue, 22 Jun 2010 13:02:56 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>, "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Date: Tue, 22 Jun 2010 13:02:51 +1000
Thread-Topic: OAuth discovery draft?
Thread-Index: AcsMLfi0k1bL/UTuTyKlbQqO9cCDCgFh6zFg
Message-ID: <255B9BB34FB7D647A506DC292726F6E1126427308C@WSMSG3153V.srv.dir.telstra.com>
References: <90C41DD21FB7C64BB94121FBBC2E72343B3EBB68D9@P3PW5EX1MB01.EX1.SECURESERVER.NET>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343B3EBB68D9@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-cr-puzzleid: {4CD628C3-3E13-4620-9930-B167B6A79BF8}
x-cr-hashedpuzzle: A3da Ci0J C5B5 ELIy EhyX FR/3 F1D9 KIZ9 LD7C MqSL NYs5 OGMW PMZI QdFM Q7n3 U0bb; 2; ZQByAGEAbgBAAGgAdQBlAG4AaQB2AGUAcgBzAGUALgBjAG8AbQA7AG8AYQB1AHQAaABAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {4CD628C3-3E13-4620-9930-B167B6A79BF8}; agBhAG0AZQBzAC4AaAAuAG0AYQBuAGcAZQByAEAAdABlAGEAbQAuAHQAZQBsAHMAdAByAGEALgBjAG8AbQA=; Tue, 22 Jun 2010 03:02:51 GMT; TwBBAHUAdABoACAAZABpAHMAYwBvAHYAZQByAHkAIABkAHIAYQBmAHQAPwA=
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [OAUTH-WG] OAuth discovery draft?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jun 2010 03:02:52 -0000

Eran,

There have been a few mentions recently of an OAuth discovery draft. Is there any such draft yet, or is this just a part that we know needs to be done?

The email on "OAuth meeting notes on -05 (with updates)" said:

>> 6.1.1. - describing the WWW-Authenticate response header
>>
>> - Discovery needed for various elements
>
> Yes. That's for the discovery draft.


A wiki page on "Future OpenID Technical Requirements" <http://wiki.openid.net/Future-OpenID-Technical-Requirements> says:

> 6) IdP Discovery
>
>    * Much of this will be covered by OAuth2 Discovery,
>      however OIC may need to define OpenID specific features.
>…
> 17) Simpler discovery
>
>    * See Eran's OAuth Discovery proposal


There was an OAuth 1.0 Discovery draft over 2 years ago, but that is tagged: "expired", "marked as obsolete by its author", "discouraged from implementing", "no update is expected", "replaced by the OAuth 2.0 effort".

I know I should write a discovery draft myself.

-- 
James Manger

v2.43.4 | Report a Bug | By Email | System Status