Re: [OAUTH-WG] Registered token_endpoint_auth_method with bearer assertion grant

Brian Campbell <bcampbell@pingidentity.com> Tue, 10 November 2015 13:10 UTC

Return-Path: <bcampbell@pingidentity.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82EEA1A911F for <oauth@ietfa.amsl.com>; Tue, 10 Nov 2015 05:10:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 vz8sVF08seF2 for <oauth@ietfa.amsl.com>; Tue, 10 Nov 2015 05:10:30 -0800 (PST)
Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::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 102E41ACDE0 for <oauth@ietf.org>; Tue, 10 Nov 2015 05:10:30 -0800 (PST)
Received: by igl9 with SMTP id 9so52839797igl.0 for <oauth@ietf.org>; Tue, 10 Nov 2015 05:10:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=gmail; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=/cTWG+9SQ06gsrU7e88oyk8fbY0lL8C9qEnyzrO/nUg=; b=mKhD2RN0TU7/XumJts1jPAkf5CKqJZUwhU0wFA6O8SGEJyPOCmYET3EbtRxdeeDRBF SBqZgCl3vJ9r2FqAyKuPq0XuYs9WHigwb7nBqFwwDhL24ED00mmcxLVUOSVgYksjcngQ pFXPSmAuYDHOpxrWtdCHribewbodsR68s6WIw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=/cTWG+9SQ06gsrU7e88oyk8fbY0lL8C9qEnyzrO/nUg=; b=RQsQDrW3G6rePHBkC02P2LKzwbYnx++gqfVwjm8r5Ji9H8GGZR93BmQ2qZSm9zT0DJ nbHDPgNc1Td9EsTK3x7jCvvJQU9yDPzJvkTcnNPOuCn3SSlDJfynkoT7LNe/DjvhZ8o7 YfUgJhKEolsw/1tc3gJEkG9lf1KONSVLLHmBuTbkaZMImR1FfV6uJmEB4wnWiP/DiUMz mb4df+4ZP6RydMmVhIIqLGMntHmIyd00bip8jjkHL0nokOUxspgu9l28Kb5UHmGkirLl MsoTuHyL7PrJAdu7OWJAk+E9ZwUHfclDgKCewfpAg4DdZuSJT2fPTKZhIcxQlDza2agQ id7w==
X-Gm-Message-State: ALoCoQkxOgb08mlK7sEexk1NdKaA/I8Xsmf5CtLXxCNxgneloGdHfPVNss0bCbK7swEVwcOoqByr
X-Received: by 10.50.79.231 with SMTP id m7mr3673512igx.57.1447161029286; Tue, 10 Nov 2015 05:10:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.117.132 with HTTP; Tue, 10 Nov 2015 05:09:59 -0800 (PST)
In-Reply-To: <5641B0DE.3050501@connect2id.com>
References: <5641B0DE.3050501@connect2id.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Tue, 10 Nov 2015 06:09:59 -0700
Message-ID: <CA+k3eCS7ZHp1mgC_XuF=1F0oEPbAZWJwXDpdAoRHe=_zwPkcJw@mail.gmail.com>
To: Vladimir Dzhuvinov <vladimir@connect2id.com>
Content-Type: multipart/alternative; boundary=089e013a06bc15a14105242f6f9b
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/_-XNJ-UDKjMJj1oOVHyIqrhVewk>
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Registered token_endpoint_auth_method with bearer assertion grant
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 10 Nov 2015 13:10:32 -0000

Despite the text in RFC 7591, IMHO "none" is still what you'd use here -
"none" describes what will be used for explicit client authentication. And
that's what the AS needs to know.

On Tue, Nov 10, 2015 at 1:54 AM, Vladimir Dzhuvinov <vladimir@connect2id.com
> wrote:

> Hi,
>
> I've got a query regarding a use case:
>
> 1. Client with self-issued JWT bearer assertion grant
> 2. No explicit client auth, i.e. authentication is done via the presented
> JWT grant
>
> What value should then the *token_endpoint_auth_method* reg parameter for
> the client have?
>
> "none" is apparently reserved for public clients:
> http://tools.ietf.org/html/rfc7591#section-2
>
> Empty value perhaps?
>
> Thanks,
>
> Vladimir
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>