IETF Logo Mail Archive

Re: [kitten] On SASL's authzid

"Cantor, Scott" <cantor.2@osu.edu> Mon, 10 March 2014 17:27 UTC

Return-Path: <cantor.2@osu.edu>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CDA01A06B8 for <kitten@ietfa.amsl.com>; Mon, 10 Mar 2014 10:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 GcrfDMctr0ZK for <kitten@ietfa.amsl.com>; Mon, 10 Mar 2014 10:27:03 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe004.messaging.microsoft.com [216.32.181.184]) by ietfa.amsl.com (Postfix) with ESMTP id A82601A06B2 for <kitten@ietf.org>; Mon, 10 Mar 2014 10:27:02 -0700 (PDT)
Received: from mail161-ch1-R.bigfish.com (10.43.68.243) by CH1EHSOBE022.bigfish.com (10.43.70.79) with Microsoft SMTP Server id 14.1.225.22; Mon, 10 Mar 2014 17:26:57 +0000
Received: from mail161-ch1 (localhost [127.0.0.1]) by mail161-ch1-R.bigfish.com (Postfix) with ESMTP id E06372000FA; Mon, 10 Mar 2014 17:26:56 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:164.107.81.208; KIP:(null); UIP:(null); IPV:NLI; H:cio-krc-pf01; RD:none; EFVD:NLI
X-SpamScore: 4
X-BigFish: VPS4(zzbb2dI98dI9371Izz1f42h1d77h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz1de098h8275bh1de097hz2fh109h2a8h839h944he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h2216h22d0h2336h2438h2461h2476h2487h24d7h2516h2545h255eh25cch25f6h2605h1b1cn1b1bi1155h)
Received-SPF: pass (mail161-ch1: domain of osu.edu designates 164.107.81.208 as permitted sender) client-ip=164.107.81.208; envelope-from=cantor.2@osu.edu; helo=cio-krc-pf01 ; cio-krc-pf01 ;
Received: from mail161-ch1 (localhost.localdomain [127.0.0.1]) by mail161-ch1 (MessageSwitch) id 1394472407715695_21668; Mon, 10 Mar 2014 17:26:47 +0000 (UTC)
Received: from CH1EHSMHS032.bigfish.com (snatpool3.int.messaging.microsoft.com [10.43.68.225]) by mail161-ch1.bigfish.com (Postfix) with ESMTP id A9AC42602FC; Mon, 10 Mar 2014 17:26:47 +0000 (UTC)
Received: from cio-krc-pf01 (164.107.81.208) by CH1EHSMHS032.bigfish.com (10.43.70.32) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 10 Mar 2014 17:26:46 +0000
Received: from CIO-KRC-HT02.osuad.osu.edu (localhost [127.0.0.1]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by cio-krc-pf01 (Postfix) with ESMTPS id 90421A0069; Mon, 10 Mar 2014 13:26:45 -0400 (EDT)
Received: from CIO-KRC-D1MBX01.osuad.osu.edu ([fe80::450b:35e6:80f4:f3e0]) by CIO-KRC-HT02.osuad.osu.edu ([fe80::8554:1787:2a7:72c9%12]) with mapi id 14.03.0174.001; Mon, 10 Mar 2014 13:26:45 -0400
From: "Cantor, Scott" <cantor.2@osu.edu>
To: Ryan Troll <rtroll@googlers.com>, William Mills <wmills_92105@yahoo.com>
Thread-Topic: [kitten] On SASL's authzid
Thread-Index: AQHPOanJU7MgJYkHMUqid6fG1ztCiJrVisiAgAB8cgCAACBAgIAAPI8AgAADUQCAAAdPAIAAEpaA//+uhgCAAFWxAP//rbuAgABUoACABFJIAP//zyiA
Date: Mon, 10 Mar 2014 17:26:44 +0000
Message-ID: <CF436DAF.4B41B%cantor.2@osu.edu>
References: <CF3FAF4D.4B1F4%cantor.2@osu.edu> <1394230922.9009.YahooMailAndroidMobile@web142803.mail.bf1.yahoo.com> <CAPe4Cjp6KSL5FsHVzNPMxvE_E4BmaWgEuZQVr_wEkexH=ukpAg@mail.gmail.com>
In-Reply-To: <CAPe4Cjp6KSL5FsHVzNPMxvE_E4BmaWgEuZQVr_wEkexH=ukpAg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [128.146.178.26]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8012A40E7C4CAD458D5A594AE537A2CE@osu.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-OriginatorOrg: osu.edu
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Archived-At: http://mailarchive.ietf.org/arch/msg/kitten/947SWpzn_Xer5HUW7LOstpQsxpw
Cc: "kitten@ietf.org" <kitten@ietf.org>
Subject: Re: [kitten] On SASL's authzid
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Mar 2014 17:27:06 -0000

On 3/10/14, 1:21 PM, "Ryan Troll" <rtroll@googlers.com> wrote:

>Google uses the user= field as an authzid.  It identifies the mailbox
>being accessed, and the session terminates at the server responsible for
>that mailbox.
>In the future, if a client provided users with the ability to log in as
>user A and read mailbox B, we would want to know identity B.  Which
>certainly appears to be the authzid.
>Scott - does this help?

It helps me, in the sense that both those use cases seem pretty clearly
exactly what authzid is. They have literally nothing to do with OAuth or
this mechanism, and would apply to any mechanism Google supported.

-- Scott

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