IETF Logo Mail Archive

Re: [OAUTH-WG] Resource Indicators Implementations

Brian Campbell <bcampbell@pingidentity.com> Mon, 07 January 2019 17:48 UTC

Return-Path: <bcampbell@pingidentity.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 A5F85130FCF for <oauth@ietfa.amsl.com>; Mon, 7 Jan 2019 09:48:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key) header.d=pingidentity.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 v9moNnMmzchA for <oauth@ietfa.amsl.com>; Mon, 7 Jan 2019 09:48:22 -0800 (PST)
Received: from mail-it1-x12f.google.com (mail-it1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (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 56647130FC7 for <oauth@ietf.org>; Mon, 7 Jan 2019 09:48:22 -0800 (PST)
Received: by mail-it1-x12f.google.com with SMTP id b5so2240893iti.2 for <oauth@ietf.org>; Mon, 07 Jan 2019 09:48:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=gmail; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/LS26OupOmGYIA8DPVjIQVNnG/BTOKKun2W+oc1uc+g=; b=JX+TxRRbb8Ix1UD5tR97aHHkGDSAnwOE5qlbpWA82YqNvg+jiCFkoJ13PJhSiP+e4m MHpWOu4e5anN2P2bImqSZEAv7k4Ui06YFulmPQFvUNKNoYb7JEITdtaKZSNBKj0a0dDb tTYVx9+/HxdubTD73zhKmtglTmhRXVDbiBEnE=
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=/LS26OupOmGYIA8DPVjIQVNnG/BTOKKun2W+oc1uc+g=; b=OZxrCniXkRzGww09CoSuR2loOiqxZ+fyqHc1CpfAPkjQHLnkS9chaEKZHqlrPNq2AR aNytI31N1PAkLBeGaCKQqlHZqpsNI5+a9xle94tTvfO7wUWVtkHa8+dw8LE9g4L5NOBW BvaD0RwtakccVf4RqEYZhi+DdZI5a6NwaS03j4lRa8s51o0IR7llAOhed0W+mLDt4pXI g7G/iU7TxLDogQfvujZkKLeCjiQN832l69ZJtZQiif9FcluwFxDYUTXG/hT/HxemN5EJ Jhtu2tBaX96ODweYcrndczIMTWQpiiaZpjuvzHN3EIBInzlPrRjXGRoht6eN9jl98Z1G +YOA==
X-Gm-Message-State: AJcUukdRsdKhP26GxL2FliuEEYDafxtcJBjW8/tJqPt86TShx7S2WMZI teeujWr6AkEMrroANsIqkhTOCaQwsuBvhczQgRps0RUoYlvCKPl7kUSsrn2zql8unxb31d1DhOp zkHSbgkhsXXe+Hg==
X-Google-Smtp-Source: ALg8bN7iFLPhSqlIqchcfgsZe3FA6WUragT6vtm+Oo4SdPBFn4LoTJfBW8A5i9C5f6dxSfD6ZX9f+2FTCTw0Z1Ci2Mg=
X-Received: by 2002:a24:8ac7:: with SMTP id v190mr7830966itd.174.1546883301236; Mon, 07 Jan 2019 09:48:21 -0800 (PST)
MIME-Version: 1.0
References: <CAGL6ep+tMj0BpS5XPQwSdRymZDm3UgShhzTcQ3XRK-21T+X5Yg@mail.gmail.com>
In-Reply-To: <CAGL6ep+tMj0BpS5XPQwSdRymZDm3UgShhzTcQ3XRK-21T+X5Yg@mail.gmail.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Mon, 07 Jan 2019 10:47:55 -0700
Message-ID: <CA+k3eCSaguUWNO8530xe=MeR7EbF2EvDv_kFO-U2kTUcSesKRQ@mail.gmail.com>
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Cc: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000adfed3057ee1d5d2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/guuZUqaHNTzI12sdlF8GlB1vkqc>
Subject: Re: [OAUTH-WG] Resource Indicators Implementations
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: Mon, 07 Jan 2019 17:48:25 -0000

Ping has an implementation that was done years ago but using a different
parameter name (see 'aud' at
https://documentation.pingidentity.com/pingfederate/pf92/index.shtml#adminGuide/tokenEndpoint.html
for one example). So it's not this exact draft per se but is conceptually
the same. And problems encountered using 'aud' as the name helped inform
the direction of the draft. So it's very much related and running code and
all that.

My understanding is that Microsoft has an implementation. I'm no authority
on their stuff but, for example, you can see usage of the parameter in this
documentation of the code flow:
https://docs.microsoft.com/en-us/azure/active-directory/develop/v1-protocols-oauth-code

On Fri, Jan 4, 2019 at 8:39 AM Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
wrote:

> All,
>
> As part of the write-up for the Resource Indicators document, we are
> looking for information about implementations for this document.
> https://datatracker.ietf.org/doc/draft-ietf-oauth-resource-indicators/
>
> Please, let us know if you are aware of any implementation for this draft.
>
> Regards,
>  Rifaat & Hannes
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

-- 
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately 
by e-mail and delete the message and any file attachments from your 
computer. Thank you._

v2.23.0 | Report a Bug | By Email