IETF Logo Mail Archive

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

"Phil Hunt (IDM)" <phil.hunt@oracle.com> Sat, 12 March 2016 19:37 UTC

Return-Path: <phil.hunt@oracle.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 E4E4012D807 for <oauth@ietfa.amsl.com>; Sat, 12 Mar 2016 11:37:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 DP2xXk3juwn5 for <oauth@ietfa.amsl.com>; Sat, 12 Mar 2016 11:37:00 -0800 (PST)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D967D12D805 for <oauth@ietf.org>; Sat, 12 Mar 2016 11:36:59 -0800 (PST)
Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u2CJawGk010579 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 12 Mar 2016 19:36:58 GMT
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0022.oracle.com (8.14.4/8.13.8) with ESMTP id u2CJawIs018876 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 12 Mar 2016 19:36:58 GMT
Received: from abhmp0005.oracle.com (abhmp0005.oracle.com [141.146.116.11]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u2CJavc0012787; Sat, 12 Mar 2016 19:36:57 GMT
Received: from [192.168.1.23] (/174.7.250.104) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 12 Mar 2016 11:36:57 -0800
Content-Type: multipart/alternative; boundary="Apple-Mail-A2A18886-9CF0-4981-A64B-D0656C45118E"
Mime-Version: 1.0 (1.0)
From: "Phil Hunt (IDM)" <phil.hunt@oracle.com>
X-Mailer: iPhone Mail (13D20)
In-Reply-To: <CAB3ntOvvZ=DVmpDvO5jo5HA7t+c=CdWX4t7vp5xD4q2crhwDrg@mail.gmail.com>
Date: Sat, 12 Mar 2016 11:36:56 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <AF7F0D51-E81D-486D-A9AB-BB8DBF2F63B6@oracle.com>
References: <mailman.755.1457798793.7781.oauth@ietf.org> <c84c120940a533c1fc96b35a8a062a0d@gluu.org> <CAB3ntOtBkzVnffoC_wFR42EDo4bmRcJZkbu+vgp=0Vi8EU1png@mail.gmail.com> <E1067E57-576D-4551-AB98-5A0911DDE310@oracle.com> <CAB3ntOvvZ=DVmpDvO5jo5HA7t+c=CdWX4t7vp5xD4q2crhwDrg@mail.gmail.com>
To: Jim Willeke <jim@willeke.com>
X-Source-IP: userv0022.oracle.com [156.151.31.74]
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/RD78HaZ0_19xcAq9K-Rk92JT86o>
Cc: oauth@ietf.org
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 19:37:02 -0000

Right now we are discussing mis-configured clients that have been convinced to use a token or rs endpoint that has been mitm. Adding a new parameter increases attack surface because the rs is now ignoring the token abd believing the header which may have been inserted. 

Phil

> On Mar 12, 2016, at 11:29, Jim Willeke <jim@willeke.com> wrote:
> 
> Would a header be a concern if TLS was used for transportation?
> 
> --
> -jim
> Jim Willeke
> 
>> On Sat, Mar 12, 2016 at 10:03 AM, Phil Hunt (IDM) <phil.hunt@oracle.com> wrote:
>> A header might open another attack vector. Better to parse the jwt and look for the issuer assuming the jwt validates. 
>> 
>> Phil
>> 
>>> On Mar 12, 2016, at 09:02, Jim Willeke <jim@willeke.com> wrote:
>>> 
>>> Why not register JWT as an access token type 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
>>> 
>>> _______________________________________________
>>> OAuth mailing list
>>> OAuth@ietf.org
>>> https://www.ietf.org/mailman/listinfo/oauth
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email