IETF Logo Mail Archive

Re: [OAUTH-WG] Report an authentication issue

Lewis Adam-CAL022 <Adam.Lewis@motorolasolutions.com> Thu, 21 June 2012 19:06 UTC

Return-Path: <Adam.Lewis@motorolasolutions.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 6744111E80BC for <oauth@ietfa.amsl.com>; Thu, 21 Jun 2012 12:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.166
X-Spam-Level:
X-Spam-Status: No, score=-0.166 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_LOW=-1, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B+t95Vp0LpCd for <oauth@ietfa.amsl.com>; Thu, 21 Jun 2012 12:05:59 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe001.messaging.microsoft.com [213.199.154.139]) by ietfa.amsl.com (Postfix) with ESMTP id 95E3E21F8622 for <oauth@ietf.org>; Thu, 21 Jun 2012 12:05:58 -0700 (PDT)
Received: from mail120-db3-R.bigfish.com (10.3.81.237) by DB3EHSOBE003.bigfish.com (10.3.84.23) with Microsoft SMTP Server id 14.1.225.23; Thu, 21 Jun 2012 19:04:29 +0000
Received: from mail120-db3 (localhost [127.0.0.1]) by mail120-db3-R.bigfish.com (Postfix) with ESMTP id AECFF1004C5 for <oauth@ietf.org>; Thu, 21 Jun 2012 19:04:29 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:192.160.210.12; KIP:(null); UIP:(null); IPV:NLI; H:CT11GSG01.am.mot-solutions.com; RD:ct11gsg01.mot-solutions.com; EFVD:NLI
X-SpamScore: 0
X-BigFish: VPS0(zzc85fhzz1202hzz8275bh8275dhz2fh2a8h683h839hd25hf0ah)
Received-SPF: pass (mail120-db3: domain of motorolasolutions.com designates 192.160.210.12 as permitted sender) client-ip=192.160.210.12; envelope-from=Adam.Lewis@motorolasolutions.com; helo=CT11GSG01.am.mot-solutions.com ; olutions.com ;
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.234.85; KIP:(null); UIP:(null); (null); H:SN2PRD0410HT005.namprd04.prod.outlook.com; R:internal; EFV:INT
Received: from mail120-db3 (localhost.localdomain [127.0.0.1]) by mail120-db3 (MessageSwitch) id 1340305467301618_8022; Thu, 21 Jun 2012 19:04:27 +0000 (UTC)
Received: from DB3EHSMHS007.bigfish.com (unknown [10.3.81.233]) by mail120-db3.bigfish.com (Postfix) with ESMTP id 47B983A0259 for <oauth@ietf.org>; Thu, 21 Jun 2012 19:04:27 +0000 (UTC)
Received: from CT11GSG01.am.mot-solutions.com (192.160.210.12) by DB3EHSMHS007.bigfish.com (10.3.87.107) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 21 Jun 2012 19:04:25 +0000
Received: from CT11GSG01.am.mot-solutions.com (ct11vts02.am.mot.com [10.177.16.160]) by CT11GSG01.am.mot-solutions.com (8.14.3/8.14.3) with ESMTP id q5LJ9IP7019211 for <oauth@ietf.org>; Thu, 21 Jun 2012 15:09:18 -0400 (EDT)
Received: from CH1EHSOBE003.bigfish.com (ch1ehsobe005.messaging.microsoft.com [216.32.181.185]) by CT11GSG01.am.mot-solutions.com (8.14.3/8.14.3) with ESMTP id q5LJ9IcX019205 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <oauth@ietf.org>; Thu, 21 Jun 2012 15:09:18 -0400 (EDT)
Received: from mail187-ch1-R.bigfish.com (10.43.68.235) by CH1EHSOBE003.bigfish.com (10.43.70.53) with Microsoft SMTP Server id 14.1.225.23; Thu, 21 Jun 2012 19:04:22 +0000
Received: from mail187-ch1 (localhost [127.0.0.1]) by mail187-ch1-R.bigfish.com (Postfix) with ESMTP id 09EB43C00B5 for <oauth@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Thu, 21 Jun 2012 19:04:22 +0000 (UTC)
Received: from mail187-ch1 (localhost.localdomain [127.0.0.1]) by mail187-ch1 (MessageSwitch) id 1340305461379409_22093; Thu, 21 Jun 2012 19:04:21 +0000 (UTC)
Received: from CH1EHSMHS004.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.246]) by mail187-ch1.bigfish.com (Postfix) with ESMTP id 5A7D6E0061; Thu, 21 Jun 2012 19:04:21 +0000 (UTC)
Received: from SN2PRD0410HT005.namprd04.prod.outlook.com (157.56.234.85) by CH1EHSMHS004.bigfish.com (10.43.70.4) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 21 Jun 2012 19:04:20 +0000
Received: from SN2PRD0410MB370.namprd04.prod.outlook.com ([169.254.7.46]) by SN2PRD0410HT005.namprd04.prod.outlook.com ([10.255.115.40]) with mapi id 14.16.0164.004; Thu, 21 Jun 2012 19:05:47 +0000
From: Lewis Adam-CAL022 <Adam.Lewis@motorolasolutions.com>
To: Nat Sakimura <sakimura@gmail.com>
Thread-Topic: [OAUTH-WG] Report an authentication issue
Thread-Index: AQHNT8xFtcJvIS3+iUqysAsMD9SHi5cFHAEA
Date: Thu, 21 Jun 2012 19:05:46 +0000
Message-ID: <59E470B10C4630419ED717AC79FCF9A917054D88@SN2PRD0410MB370.namprd04.prod.outlook.com>
References: <CAEEmcpEcNqNHwfVozD-NtfkruiB-v0MTszwNL4cob2rL=QQTSA@mail.gmail.com> <CABzCy2BZLff7EZoWaU+vmCWCgXUSSxn3x-evm-FwzKdnx7QeMA@mail.gmail.com> <1339792496.52712.YahooMailNeo@web125501.mail.ne1.yahoo.com> <CABzCy2APCsGU9N00K4XYoa4Scxno51b_E=8MKD9MzZk6zxtc1Q@mail.gmail.com> <BDF3CDE9-B411-4366-9C5F-C3EA17938C21@matake.jp> <C05B5190-B0B7-42AD-A6DB-FABF190D2674@gmail.com> <59E470B10C4630419ED717AC79FCF9A9108898EE@BL2PRD0410MB363.namprd04.prod.outlook.com> <4FE223E4.6060307@mitre.org> <4FE226BC.6010403@alcatel-lucent.com> <59E470B10C4630419ED717AC79FCF9A910889AB5@BL2PRD0410MB363.namprd04.prod.outlook.com> <CABzCy2CLe_DVcxiD1EasuhtG1_6+6tCtV5TckZ80fvqyjan_bA@mail.gmail.com> <59E470B10C4630419ED717AC79FCF9A917052BC8@SN2PRD0410MB370.namprd04.prod.outlook.com> <CABzCy2CqsX12rcM34ZodSubf5+_zYRUyqmtrMs4L9_20Rsetng@mail.gmail.com>
In-Reply-To: <CABzCy2CqsX12rcM34ZodSubf5+_zYRUyqmtrMs4L9_20Rsetng@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [150.130.45.131]
Content-Type: multipart/alternative; boundary="_000_59E470B10C4630419ED717AC79FCF9A917054D88SN2PRD0410MB370_"
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%1294$Dn%GMAIL.COM$RO%2$TLS%3$FQDN%msgate.mot-solutions.com$TlsDn%
X-FOPE-CONNECTOR: Id%1294$Dn%ALCATEL-LUCENT.COM$RO%2$TLS%3$FQDN%msgate.mot-solutions.com$TlsDn%
X-FOPE-CONNECTOR: Id%1294$Dn%IETF.ORG$RO%2$TLS%3$FQDN%msgate.mot-solutions.com$TlsDn%
X-CFilter-Loop: Reflected
X-OriginatorOrg: motorolasolutions.com
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Report an authentication issue
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: <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, 21 Jun 2012 19:06:00 -0000

Hi Nat ...

It could also be that RS is the PDP+PEP. Your model seem to fit this one.

<acl> Yes, exactly!

Then, you just take id_token there and PDP portion of the RS gives you the access token, which you present it to the PEP portion of the RS.

<acl> if by "you" you're referring to the native client, the this is EXACTLY what I want to do.


1.      User launches native client on iPhone

2.      Native client (via UA) triggers Authorization Request (response_type=id_token) to OpenID Connect provider.

3.      OpenID Connect provider authenticates user

4.      Id_token is returned to the native client via the UA in Response message

5.      Native client includes id_token in RESTful API calls to the RS

6.      RS uses subject of id_token to make authorization decision.

It seems that every time I describe this, I get a mix of responses ranging from "that's not the intended usage of the id_token" to "sounds like that should work."  This is giving me a great deal of pause.



In this case, I think id_token should be audience restricted to the RS.

<acl> absolutely!

v2.23.0 | Report a Bug | By Email