IETF Logo Mail Archive

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

Michael D Adams <mike@automattic.com> Wed, 07 July 2010 05:19 UTC

Return-Path: <michael.d.adams@gmail.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 9C7493A6873 for <oauth@core3.amsl.com>; Tue, 6 Jul 2010 22:19:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 wpBA0v8J-SiI for <oauth@core3.amsl.com>; Tue, 6 Jul 2010 22:18:58 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 1BBF23A681E for <oauth@ietf.org>; Tue, 6 Jul 2010 22:18:58 -0700 (PDT)
Received: by iwn38 with SMTP id 38so1868162iwn.31 for <oauth@ietf.org>; Tue, 06 Jul 2010 22:19:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type; bh=sUe3DF+btvVoxsPucq7YoL20eZYM2sXGuQxG71Zdnyk=; b=mgN9zLGlbQVWeDC6n9LhdegNtP1VODQ799Ug5VbhRfLnPZlIqnqEm6+0+mCa32/rZc uQPa+1YFPJPUOfBqWSg6HQK3oEDLZej5J1nnKJ2ZMt5azOpihdgcyETdwLNHNM2QSxIl tn9ik67Tvv9+3BP6SaoEeK1xQGv5O8THlvr/I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=hRvxaJy3nBGml6dCvankhKfwEsjgtbHWkvY/rG9++/auTZi+wSMHterGXPGNeJ0rRW ONJEJ4foMUbw9ClQKUJMw4m9NgjWPiDyq/5xlsLFdEDS5lhpfreFLnZX3RX1J4WymBIu bePq8RdJIO8AGkRGdSukwvrhpy2Qaqi3imcxk=
Received: by 10.231.30.129 with SMTP id u1mr6323884ibc.63.1278479940294; Tue, 06 Jul 2010 22:19:00 -0700 (PDT)
MIME-Version: 1.0
Sender: michael.d.adams@gmail.com
Received: by 10.231.179.143 with HTTP; Tue, 6 Jul 2010 22:18:39 -0700 (PDT)
In-Reply-To: <AANLkTimWZugW68Gkg_CCYZL8TUIbtaNEAlQS7cMTTSZV@mail.gmail.com>
References: <1278439815.2445.8.camel@localhost.localdomain> <C858C2B1.36C16%eran@hueniverse.com> <AANLkTimWZugW68Gkg_CCYZL8TUIbtaNEAlQS7cMTTSZV@mail.gmail.com>
From: Michael D Adams <mike@automattic.com>
Date: Tue, 06 Jul 2010 22:18:39 -0700
X-Google-Sender-Auth: Hp4zE19gb4_2gGCQHwcr9KSGHqQ
Message-ID: <AANLkTimsxRHsXggcEsQhgD04YgbdUlrm_rojSi_SLc-X@mail.gmail.com>
To: Marius Scurtescu <mscurtescu@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
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: Wed, 07 Jul 2010 05:19:07 -0000

>> 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.
>
> I don't think these are random at all. MediaWiki, Drupal, WordPress,
> to name a few, are major platforms.

For section 6.2 (query parameters on the end-user authorization and
token endpoints), this should not be an issue for WordPress.

For section 6.3 (header parameters), this should not be an issue for WordPress.

The only place this could be problematic is adding query parameters on
the protected resources themselves.

Mike
--mdawaffe

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