[OAUTH-WG] token endpoint: 400 or 401?
Ofer Nave <odigity@gmail.com> Sat, 24 October 2015 02:23 UTC
Return-Path: <odigity@gmail.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 954831B2EFE for <oauth@ietfa.amsl.com>; Fri, 23 Oct 2015 19:23:43 -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, SPF_PASS=-0.001] 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 gaceC2HwVc-j for <oauth@ietfa.amsl.com>; Fri, 23 Oct 2015 19:23:42 -0700 (PDT)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (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 3B7BE1B2EFB for <oauth@ietf.org>; Fri, 23 Oct 2015 19:23:42 -0700 (PDT)
Received: by wicll6 with SMTP id ll6so52381509wic.1 for <oauth@ietf.org>; Fri, 23 Oct 2015 19:23:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=FRkOVbu9dJnsRArTeVoPCNyjHPEtT+r/+CS9DjTZOp8=; b=sKVIPtLQ/DFJaENvI+s3GX4eGf9/Tvlh7dtd6EprWQgoxEerqcob+tjpbW5LkVp3IQ Wyiw0yYvFaaw1A2Kh1c/I1Nfp6v7OErJX0e5LtS/HCVWxj8JEngDZUCaKaxZUeTap+I9 Md/rhdBMbotkR711wQLzZFbaB7vGJq2zpPTnB0agCIKksgt2BmMRVfPmci4Nu5IyFGVo 5EzrIXk4/9u0Ajhoex6isAIRjl817Q3OVCTURofHWYJuqCxOC/h2nCui3Zd1DsKsoa+Y uYI+0NyhlX1Ap7yGn8/JM1WBESO+BNKq5Fo+8SgKoDAJnt0kjVsuQz33HtX/RVxwUhxi ilXA==
MIME-Version: 1.0
X-Received: by 10.194.123.132 with SMTP id ma4mr7326485wjb.140.1445653420859; Fri, 23 Oct 2015 19:23:40 -0700 (PDT)
Received: by 10.27.125.70 with HTTP; Fri, 23 Oct 2015 19:23:40 -0700 (PDT)
Date: Fri, 23 Oct 2015 22:23:40 -0400
Message-ID: <CABPN19-CX9AGrLOTWZrkcuP9xMj7wnuEZbs38OqLSFjnpv+Qfg@mail.gmail.com>
From: Ofer Nave <odigity@gmail.com>
To: "<oauth@ietf.org>" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="089e0118310e9e69fa0522d06adc"
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/4jAW2oLApkSFee_ajivmtmGRKLo>
Subject: [OAUTH-WG] token endpoint: 400 or 401?
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: Sat, 24 Oct 2015 02:23:43 -0000
I'm using the auth code flow, and supporting basic auth for client auth on the token endpoint. In the OAuth spec it says to respond with 400 and a json body with error: invalid_client if client auth fails. However, doesn't RFC 2617 say to respond with 401 and a WWW-Authenticate header? Does the OAuth spec supercede 2617 in this case? -ofer
- [OAUTH-WG] token endpoint: 400 or 401? Ofer Nave
- Re: [OAUTH-WG] token endpoint: 400 or 401? Vladimir Dzhuvinov