IETF Logo Mail Archive

Re: [OAUTH-WG] register prefixes as opposed to full parameter names

Eran Hammer-Lahav <eran@hueniverse.com> Tue, 06 July 2010 18:23 UTC

Return-Path: <eran@hueniverse.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 AD6D93A688A for <oauth@core3.amsl.com>; Tue, 6 Jul 2010 11:23:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.603
X-Spam-Level:
X-Spam-Status: No, score=-1.603 tagged_above=-999 required=5 tests=[AWL=-0.494, BAYES_05=-1.11, HTML_MESSAGE=0.001]
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 ic9W+r02MtOt for <oauth@core3.amsl.com>; Tue, 6 Jul 2010 11:23:32 -0700 (PDT)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id 2D2D93A67A4 for <oauth@ietf.org>; Tue, 6 Jul 2010 11:23:32 -0700 (PDT)
Received: (qmail 28954 invoked from network); 6 Jul 2010 18:23:33 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.19) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 6 Jul 2010 18:23:33 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) with mapi; Tue, 6 Jul 2010 11:23:30 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Justin Richer <jricher@mitre.org>
Date: Tue, 06 Jul 2010 11:23:29 -0700
Thread-Topic: [OAUTH-WG] register prefixes as opposed to full parameter names
Thread-Index: AcsdNn4iCXzV8y1WR7C8HWb16/iAJwAAdbHA
Message-ID: <C858C2B1.36C16%eran@hueniverse.com>
In-Reply-To: <1278439815.2445.8.camel@localhost.localdomain>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C858C2B136C16eranhueniversecom_"
MIME-Version: 1.0
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] register prefixes as opposed to full parameter names
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, 06 Jul 2010 18:23:33 -0000

Platforms change over time. These platforms are not designed with providing APIs and web services in mind. They are also typically not capable of running over SSL (due to the self-hosted nature of most deployments). Using an apache rewrite rules might be hard for some developers, but it is a good solution when there are issues with platform limitations.

If there are actual requirements for using OAuth 2.0 with such systems, we should discuss these, but it would be silly for us to architect our work based on the limitations of random platforms.

EHL




On 7/6/10 11:10 AM, "Justin Richer" <jricher@mitre.org> wrote:

> > When receiving an OAuth request MediaWiki will have two title parameters,
> > the damage is already done.
>
> Yes, they might need to change their platform to support it. I'm ok with that.

I think this is an unfortunate hubris of the spec-defining community
here. For most people, if it comes down to "change my platform or don't
support oauth", the answer is going to be "don't support oauth".

 -- Justin

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