IETF Logo Mail Archive

Re: [OAUTH-WG] resource server id needed?

Marius Scurtescu <mscurtescu@google.com> Thu, 15 July 2010 18:15 UTC

Return-Path: <mscurtescu@google.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 65C643A67B1 for <oauth@core3.amsl.com>; Thu, 15 Jul 2010 11:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.252
X-Spam-Level:
X-Spam-Status: No, score=-105.252 tagged_above=-999 required=5 tests=[AWL=0.725, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 pvoGO1l3vZbd for <oauth@core3.amsl.com>; Thu, 15 Jul 2010 11:15:13 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 155753A6891 for <oauth@ietf.org>; Thu, 15 Jul 2010 11:15:12 -0700 (PDT)
Received: from wpaz1.hot.corp.google.com (wpaz1.hot.corp.google.com [172.24.198.65]) by smtp-out.google.com with ESMTP id o6FIFNak027791 for <oauth@ietf.org>; Thu, 15 Jul 2010 11:15:23 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1279217723; bh=0XecPkSEDkZhMeb06FcMCu+ZQh8=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=IfpE8ANnco8qEl5xeyt3zgO+flxWKyJmB66W2CENv/x2MjuKABHs1/oi7/YSYX1H3 v7WRuIOzBwN8INFLdEL7w==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=oSqOHTfS9KagCa/62WmlIFs8Zd/yMEKwEfLBR36OxOqRlZiyeI+6ZQdSQnKXv1/en UijNSkYXbQTQfhU4FBlzA==
Received: from gxk27 (gxk27.prod.google.com [10.202.11.27]) by wpaz1.hot.corp.google.com with ESMTP id o6FIFMcb023018 for <oauth@ietf.org>; Thu, 15 Jul 2010 11:15:22 -0700
Received: by gxk27 with SMTP id 27so785727gxk.22 for <oauth@ietf.org>; Thu, 15 Jul 2010 11:15:22 -0700 (PDT)
Received: by 10.100.8.5 with SMTP id 5mr18927anh.110.1279217716428; Thu, 15 Jul 2010 11:15:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.93.3 with HTTP; Thu, 15 Jul 2010 11:14:55 -0700 (PDT)
In-Reply-To: <4C3F3F6A.5000409@lodderstedt.net>
References: <C8645B85.372D8%eran@hueniverse.com> <4C3F3F6A.5000409@lodderstedt.net>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Thu, 15 Jul 2010 11:14:55 -0700
Message-ID: <AANLkTinIjg7MIBmEIUzV9_Uo3MDb0nXvYXJcXNeLTUCe@mail.gmail.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] resource server id needed?
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: Thu, 15 Jul 2010 18:15:15 -0000

On Thu, Jul 15, 2010 at 10:03 AM, Torsten Lodderstedt
<torsten@lodderstedt.net> wrote:
> As I have written in my reply to Marius's posting. I'm fine with including
> server ids in scopes. But this requires a definition of the scope's syntax
> and semantics in the spec. Otherwise, scope interpretation (and server
> identification) will be deployment specific.

Sure, it is deployment specific, but why is that an issue?

In your case, the authz server and all the resource servers are
managed by the same organization, right?

Do clients need to be aware of the actual resource server?

You can probably create a separate spec that defines scope syntax for
this purpose, if really needed. Does it have to be in core?

Marius

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