IETF Logo Mail Archive

Re: [OAUTH-WG] Multiple authorization servers for one resource server

Jim Willeke <jim@willeke.com> Sat, 12 March 2016 17:03 UTC

Return-Path: <jim@willeke.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACB5612D7BA for <oauth@ietfa.amsl.com>; Sat, 12 Mar 2016 09:03:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.579
X-Spam-Level:
X-Spam-Status: No, score=-1.579 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=willeke-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dEg0lVsmLwFf for <oauth@ietfa.amsl.com>; Sat, 12 Mar 2016 09:03:28 -0800 (PST)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E42CA12D7CF for <oauth@ietf.org>; Sat, 12 Mar 2016 09:03:27 -0800 (PST)
Received: by mail-yw0-x22a.google.com with SMTP id h129so124432277ywb.1 for <oauth@ietf.org>; Sat, 12 Mar 2016 09:03:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=willeke-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:cc; bh=RwOxJ3vuI8+JGau7Nmlmg7Te0g3XeeeF4HfOkilpmrE=; b=lLjN8Sub/NtLQfWj8nqOH8qU1KA+lWsYxf+l4OwyWj+PCSaImF/WEYm0t3Kp163li3 cQ3DTs1pj7+emS69uMB/TvHDEJwVrw/aU3Qol0fGEk7RU1G2MFBVIBVVf0MNK3ca2jx0 YMF17S6SjQ7QDGiWl5Ll4gIj+vq7WoN8Vao85MR9uI4VbgQHKw1KPHrkZzQBtqFyXODw aQ9bvc8fCcikeA+QrD2BracCLshB9ePPjUzC3hjWq82USE8Ty1ZCzcYYArY5jXJ9Y7Bg cik1sYGfm/OcNtbFIjynMinc4vxRCl/k3aaAYnv51GtYe4Tp4JH8DZeZ8CPTHMZvNxGd nxDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:cc; bh=RwOxJ3vuI8+JGau7Nmlmg7Te0g3XeeeF4HfOkilpmrE=; b=Mi4D3cYBaYx0sRsLnQCx+Cli5Bt68vIo4MVtK3riFYIEM/ouc37X+mWEMS4DXT5sVM h9QYlda89pZK8JPzNXKMa3dPaVwJcgmZGM1ln+omOtAOOz+35yUFa6ggIJQabKNxt2tR tS6ZDwfdso78yejO5ZQoDXziKD8Pjzn/r3lDm7cJNSz+pKPWgEDRuQ6mU3ojK/CBGUjk 0Jpc1DkxTAucqdNKxRH14QOegRnMTeXHwFLc3eyE8ylx4tzWPgvCoobbWIaRKQs4rFgg 2PjPq1ostTWHvbE5MKixLYdWbyXUWrSFVOSZNV0V9EY/JKU1oCvXAnt6gNMZedGCG6dC GnLw==
X-Gm-Message-State: AD7BkJKufzuIMCJ9x0YabAHcgsxBlkQGhmGtfqUFdAtt+ln0W0vXaksnwDTdvFUA+HAyrMDpG093YRei3ygrVwRd
X-Received: by 10.37.93.137 with SMTP id r131mr8197782ybb.106.1457802207030; Sat, 12 Mar 2016 09:03:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.193.130 with HTTP; Sat, 12 Mar 2016 09:02:47 -0800 (PST)
In-Reply-To: <c84c120940a533c1fc96b35a8a062a0d@gluu.org>
References: <mailman.755.1457798793.7781.oauth@ietf.org> <c84c120940a533c1fc96b35a8a062a0d@gluu.org>
From: Jim Willeke <jim@willeke.com>
Date: Sat, 12 Mar 2016 09:02:47 -0800
Message-ID: <CAB3ntOtBkzVnffoC_wFR42EDo4bmRcJZkbu+vgp=0Vi8EU1png@mail.gmail.com>
Cc: oauth@ietf.org
Content-Type: multipart/alternative; boundary="001a1140d942b470fd052ddd06e0"
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/2KvaDz1P8dT4qZjr7XnVpLk3YhM>
Subject: Re: [OAUTH-WG] Multiple authorization servers for one resource server
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 12 Mar 2016 17:03:29 -0000

Why not register JWT as an access token type
<https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#token-types>
and then the the Issuer is implied?

--
-jim
Jim Willeke

On Sat, Mar 12, 2016 at 8:32 AM, Mike Schwartz <mike@gluu.org> wrote:

> Kawasaki-san,
>
> This is a really good question: how to know the issuer of a bearer token.
> Is there a header that could be added to specify the issuer, or other
> important metadata?
>
> - Mike
>
>
> -------------------------------------
> Michael Schwartz
> Gluu
> Founder / CEO
> mike@gluu.org
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

v2.23.0 | Report a Bug | By Email