Re: [OAUTH-WG] Examples of Auth with Profiles

Dick Hardt <dick.hardt@gmail.com> Thu, 12 November 2020 23:10 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 79FFB3A0FF6 for <oauth@ietfa.amsl.com>; Thu, 12 Nov 2020 15:10:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.994
X-Spam-Level:
X-Spam-Status: No, score=-0.994 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 2J-YJzbmy4Mu for <oauth@ietfa.amsl.com>; Thu, 12 Nov 2020 15:10:14 -0800 (PST)
Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (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 36A423A1043 for <oauth@ietf.org>; Thu, 12 Nov 2020 15:10:09 -0800 (PST)
Received: by mail-lf1-x132.google.com with SMTP id j205so11033339lfj.6 for <oauth@ietf.org>; Thu, 12 Nov 2020 15:10:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=k+FrJa7/miX4/O/swPcY3izG+UXHBSNgye+/pL+UPKM=; b=pTMt6yE+4DmLy4Um3UOaAAWyuCMYG9ZbO3P0ayE7KHyfLMTCWAaOugCYCAT4kQHO+q /4ydgWh+fuomCHObJ2I43w8LqTfmZ2y8DhYQVVi2QeoCIm8uMQH+nNgrxlIX/8zFdv/e GXhozrazzEBUf5u0bx9YvMdtWXbmt+ROVq6HTHzHmvW9eUDSxD3pSv2rmJrB9fQJLSCx pL7qQZeBQN629ccXLhfow5qbZ7906VUWrPS8/vpWKNxML9uGDXoi+ECm+GYOFjbgqJrd TuKx1r4UQHVWbc9THI7i/54ExwVBdzliLntmkmX5SlTkOiEecXOlROaDEeLsxdc0PsJ6 Ju9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=k+FrJa7/miX4/O/swPcY3izG+UXHBSNgye+/pL+UPKM=; b=f7nl6l/derri+SqNFbwSopCet0a3HDp3gRyi9b5lMq17Jr9lGnwgv4JrrhsCMCg3q2 6GHrVzn7zc3pHi+Vu76BnDNu+k42JW+RSoeDJNAWKrB5VbIbNzxCAOY2526ouhHPTK1i 7h1pIo9SrKytcElme2lJPs2CtWINzzU6365tXfVRnlPHk9Cy4o7I1jwct5LkWAFPnslE domT+1I3+kw2ZzJH4YQr9Etd8So3TKE7S657lnHfb+2qW4WoBOXtHdIdhtT028IK7c0R KvL18hNnftelDt0lgDRE8EZZrEMfoVkjzZgiQ8hKFk+WHVTTi8DxnlKqA0PtDIm8HEw4 BhhQ==
X-Gm-Message-State: AOAM530RXLeSPWayAsXFLVjgDihrX7A5yZK4JmvXXvO8lWwi2gIqNWCm oAxyAHMD3hwn9M/673AEYSDrdNIaKWDL2FrRRiJeISMbNY4=
X-Google-Smtp-Source: ABdhPJzidtq6XhrkiFVJYYhthNPutnQQeWzgjg1WPmkO4NloJWmQzBoXlQG3fW1p2pbScIDs/cRVPvpsvNBL+6v0YD0=
X-Received: by 2002:a19:6e4c:: with SMTP id q12mr642893lfk.162.1605222606866; Thu, 12 Nov 2020 15:10:06 -0800 (PST)
MIME-Version: 1.0
References: <CAKhDPzP_bkeVVR_Lez2uVTZjVjH1zC+TW5hz_-9N3GLO92fZRA@mail.gmail.com>
In-Reply-To: <CAKhDPzP_bkeVVR_Lez2uVTZjVjH1zC+TW5hz_-9N3GLO92fZRA@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Thu, 12 Nov 2020 15:09:31 -0800
Message-ID: <CAD9ie-uffnUOHQe57Qg3D9jEUUYKbroos2o8khaghUq9o3vPUg@mail.gmail.com>
To: Jeff Craig <jeffcraig=40google.com@dmarc.ietf.org>
Cc: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000448ff805b3f103e5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/BjEqJD2aBmtRkbxNlD6JUteChy8>
Subject: Re: [OAUTH-WG] Examples of Auth with Profiles
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 12 Nov 2020 23:10:21 -0000

Since there is no security boundary between profiles, the profile is just
passed as a parameter to APIs rather than have it in the access token.


ᐧ

On Thu, Nov 12, 2020 at 1:31 PM Jeff Craig <jeffcraig=
40google.com@dmarc.ietf.org> wrote:

> Hello OAuth WG,
>
> I am currently doing some research on APIs that have a Profile concept,
> something akin to Netflix's profile support where there is a single account
> with multiple sub-profiles. I am trying to determine how current APIs
> handle this use case, and evaluate any common patterns or practices that
> may exist today.
>
> Thanks.
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>