IETF Logo Mail Archive

Re: [OAUTH-WG] What to do about 'realm'

"Manger, James H" <James.H.Manger@team.telstra.com> Sun, 11 July 2010 13:11 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 DC57E3A67B2 for <oauth@core3.amsl.com>; Sun, 11 Jul 2010 06:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level:
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 ZOiOOjgIAUq3 for <oauth@core3.amsl.com>; Sun, 11 Jul 2010 06:11:59 -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 9BB2B3A67A7 for <oauth@ietf.org>; Sun, 11 Jul 2010 06:11:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.55,182,1278252000"; d="scan'208";a="7440519"
Received: from unknown (HELO ipcbni.tcif.telstra.com.au) ([10.97.216.204]) by ipoani.tcif.telstra.com.au with ESMTP; 11 Jul 2010 23:12:01 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,6039"; a="4403778"
Received: from wsmsg3704.srv.dir.telstra.com ([172.49.40.197]) by ipcbni.tcif.telstra.com.au with ESMTP; 11 Jul 2010 23:12:03 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3704.srv.dir.telstra.com ([172.49.40.197]) with mapi; Sun, 11 Jul 2010 23:12:02 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Brian Eaton <beaton@google.com>, "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Date: Sun, 11 Jul 2010 23:12:09 +1000
Thread-Topic: [OAUTH-WG] What to do about 'realm'
Thread-Index: Acsgxh/Z7W0KuAYVQwqj6GtbcPVkxQALnRIw
Message-ID: <255B9BB34FB7D647A506DC292726F6E112660D9E04@WSMSG3153V.srv.dir.telstra.com>
References: <90C41DD21FB7C64BB94121FBBC2E72343B3EC84ADE@P3PW5EX1MB01.EX1.SECURESERVER.NET> <AANLkTikLogvJAhE9LF60MDyEiqvpDM8WD8tSUr4fZLjP@mail.gmail.com>
In-Reply-To: <AANLkTikLogvJAhE9LF60MDyEiqvpDM8WD8tSUr4fZLjP@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] What to do about 'realm'
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: Sun, 11 Jul 2010 13:12:00 -0000

Brian,

> Or even just:
>
> WWW-Authenticate: OAuth2
>
> Seriously.

I seriously hope not.
It gives no chance for a client to work with a service without being pre-configured with a whole lot of service-specific knowledge -- in addition to an app-id/password.

I don't think a realm parameter adds much value to a "WWW-Auth.: OAuth2" header, other than complying with RFC2617. The header does need to provide an end-user authorization endpoint. Ideally, that one URI would be sufficient for the protocol to succeed (though currently you need to separately provide a token endpoint as well).

--
James Manger

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