Re: [OAUTH-WG] updated Distributed OAuth ID

Dick Hardt <dick.hardt@gmail.com> Mon, 23 July 2018 23:25 UTC

Return-Path: <dick.hardt@gmail.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 9A2CD130E04 for <oauth@ietfa.amsl.com>; Mon, 23 Jul 2018 16:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 WFSiIB4f0T1c for <oauth@ietfa.amsl.com>; Mon, 23 Jul 2018 16:25:31 -0700 (PDT)
Received: from mail-pl0-x229.google.com (mail-pl0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) (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 8CD15130DF1 for <oauth@ietf.org>; Mon, 23 Jul 2018 16:25:31 -0700 (PDT)
Received: by mail-pl0-x229.google.com with SMTP id o7-v6so861829plk.10 for <oauth@ietf.org>; Mon, 23 Jul 2018 16:25:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7QM/AkoCuFMHzD2BNbxOCzzAGFriehj9yxt+2ds0OIw=; b=XvRSkIr/2s0eVwqvJvR2CW/yXCF48+IpQG2GuymbZsaPasrdu6MjywLbTHssE2sB/c 8m4ch5XG2LeAvHdRZ2qwv3aEUGzsT9BbJk/3V6n/GXPiAcVGGKcrtT2vcXNqIWEVcaZj PD9dMQFFEOXvHm9Eq/YylRUJd30PPhDg8ULMzAQZ4hEsfsxINIdKApnWqXxol3NChqJa lIdo+XNaRSmEfRcdCoOfeLYmdtO6e5GKvckLy04PTSrBi/0YwhqfUgQXQggLb1YF8CDw HkXrRXGV1L1gpCcsozQ2fDpl749o26+Tqlrddal0a6xkgaD8NJQs1TCACHnefpScO+Em g1AQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7QM/AkoCuFMHzD2BNbxOCzzAGFriehj9yxt+2ds0OIw=; b=WkKrI9nP1UAzTT7ci/xoy0Fmr1T1J0l8SOdhPUM4bnGGK9g5PV5whWqwJ/5l3GKM/+ 7VAC72utR0g2gfDaPdU5HANBrgOpDwK+SoSLYWnAPMBKtVmqnKJJAPGOM0eZ8UHhvpNp w537NKVZQEbEDRGF9ogNWKNQqajB3IKQwFja65MnWfywmQUOmQdIsmN90fDXPTVnvd9d tQqvE4/onHYtaVNBC8cbUQUCWXd0hgDZcuKQ42gpCIDgX0mAbXofr7Eth0lK1wcVXBlM cTXa08QAOaIRhlk9EfVpRfSxrYoV/bBlR1Npd/pZLhG3+7cHuopuReJYjyaZCh9AVzvs TAPg==
X-Gm-Message-State: AOUpUlFBETsAr0/a93xQVSaCzVJUpi+N0M0qO9TQI5mvWISOT3LX7+5c SUV82LIkoiQL30mZB0AZ+8bisDiFL0QZM/tbopHDRg==
X-Google-Smtp-Source: AAOMgpe0WFu5HeSmdrwYPhx+PjwDIas8ClxTgxNzm9qmbXEye+H/kZWczKCqKg7xUNszbkSgE9LqTMSBhIOTR8ytG7o=
X-Received: by 2002:a17:902:b20d:: with SMTP id t13-v6mr14811969plr.121.1532388330902; Mon, 23 Jul 2018 16:25:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:150c:0:0:0:0 with HTTP; Mon, 23 Jul 2018 16:25:09 -0700 (PDT)
In-Reply-To: <0FC092A4-9E3D-4F1A-A494-9B619F90C3AA@lodderstedt.net>
References: <CAD9ie-sW7EbfuJWc8_fkLO0wGg9kd0VR=xuO346yOoMK8ZGiyQ@mail.gmail.com> <B976F6E6-95E3-4B50-A54B-C207FA4D82A7@lodderstedt.net> <CAD9ie-sUM3jQm8pN1e4wUpSAJw=DW=xDXJS--R6icpjJsnV_AA@mail.gmail.com> <3A81E7C4-5FE1-448A-BB3D-540D30BF2637@lodderstedt.net> <CAD9ie-s2nwXovWM3OfDG8MJvs+TVzX_KearbW1Uq_6Nz9X_5mg@mail.gmail.com> <419D8DCF-817B-484F-8EB7-FEB4C5BA51DC@lodderstedt.net> <CAD9ie-tNDcWdT0iwNFYoL4x+gB6Yr=QNSjAOrV7ZjwqyLaUQeQ@mail.gmail.com> <0E9E324F-D6EB-45AB-B066-BFAA87B91A21@lodderstedt.net> <CAD9ie-uXvg=bLLeK8PzhWjd_Any5cvxDisnAdy9hquLqWwR6Fw@mail.gmail.com> <0FC092A4-9E3D-4F1A-A494-9B619F90C3AA@lodderstedt.net>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Mon, 23 Jul 2018 19:25:09 -0400
Message-ID: <CAD9ie-tBrskz5OqYFqpTg1jiaeDXAte7f+SFx1Pqh8LLFVd7jQ@mail.gmail.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
Cc: oauth@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001f1c7f0571b2f68a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/mw2R_FAXZde0EqMfWTaYuGsKjsk>
Subject: Re: [OAUTH-WG] updated Distributed OAuth ID
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.27
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: Mon, 23 Jul 2018 23:25:34 -0000

And who is the AS?

On Mon, Jul 23, 2018 at 12:50 PM, Torsten Lodderstedt <
torsten@lodderstedt.net> wrote:

>
> Am 23.07.2018 um 13:58 schrieb Dick Hardt <dick.hardt@gmail.com>om>:
>
> In your examples, are these the same AS?
>
>
> yes
>
>
>
>
> On Mon, Jul 23, 2018 at 3:42 AM Torsten Lodderstedt <
> torsten@lodderstedt.net> wrote:
>
>> Hi Dick,
>>
>> > Am 23.07.2018 um 00:52 schrieb Dick Hardt <dick.hardt@gmail.com>om>:
>> >
>> > Entering in an email address that resolves to a resource makes sense.
>> It would seem that even if this was email, calendar etc. -- that those
>> would be different scopes for the same AS, not even different resources.
>> That is how all of Google, Microsoft work today.
>>
>> I don’t know how those services work re OAuth resources. To me it’s not
>> obvious why one should make all those services a single OAuth resource. I
>> assume the fact OAuth as it is specified today has no concept of
>> identifying a resource and audience restrict an access token led to designs
>> not utilizing audience restriction.
>>
>> Can any of the Google or Microsoft on this list representatives please
>> comment?
>>
>> In deployments I‘m familiar with email, calendar, contacts, cloud and
>> further services were treated as different resources and clients needed
>> different (audience restricted) access tokens to use it.
>>
>> In case of YES, the locations of a user’s services for account
>> information, payment initiation, identity, and electronic signature are
>> determined based on her bank affiliation (bank identification code). In
>> general, each of these services may be provided/operated by a different
>> entity and exposed at completely different endpoints (even different DNS
>> domains).
>>
>> kind regards,
>> Torsten.
>
>