Re: [OAUTH-WG] Fwd: New Version Notification for draft-richer-oauth-introspection-01.txt

George Fletcher <> Fri, 11 January 2013 17:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 754A621F87C3 for <>; Fri, 11 Jan 2013 09:38:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AtiDsjGzVRL3 for <>; Fri, 11 Jan 2013 09:38:06 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 67B2521F87B2 for <>; Fri, 11 Jan 2013 09:38:02 -0800 (PST)
Received: from ( []) by (Outbound Mail Relay) with ESMTP id B1CAB1C00011D; Fri, 11 Jan 2013 12:38:01 -0500 (EST)
Received: from palantir.local (unknown []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (MUA/Third Party Client Interface) with ESMTPSA id 557E7E0000C4; Fri, 11 Jan 2013 12:38:01 -0500 (EST)
Message-ID: <>
Date: Fri, 11 Jan 2013 12:38:00 -0500
From: George Fletcher <>
Organization: AOL LLC
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "" <>
References: <> <>
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="------------080503070503080602090108"
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20121107; t=1357925881; bh=BHPU8KMOblDKFAZYTDOiDEpf9K2BsiqT7ull2JffBSs=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=ANaqcLljtACtPFLZuRKtnR7RIizhK9RzJSkqXGU2ueAZrLfvB03iV9hn1qtjZ4T3/ d6vYSdqkdHpX7Idv1s9wg+73vaJ0uAWeXhkqy8Io5gxXBGotCjM+KYxnohpRb1Dxk8 mB1wOXiHGw5PIeKGMmy2jwuiEWwHbqoMm1SaJUno=
X-AOL-SCOLL-SCORE: 1:2:331456128:93952408
x-aol-sid: 3039ac1d290350f04df94c7d
Subject: Re: [OAUTH-WG] Fwd: New Version Notification for draft-richer-oauth-introspection-01.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 11 Jan 2013 17:38:07 -0000

Additional feedback on the introspection endpoint.

What is the expected error response if the introspection endpoint is 
using client credentials as recommended in section 2.1

The endpoint SHOULD also require some form of authentication to
    access this endpoint, such as the Client Authentication as described
    in OAuth 2 Core Specification [RFC6749  <>] or a separate OAuth2 Access

and the client credentials are invalid. It doesn't seem correct to 
return an HTTP 200 with a body of { "valid: false } as the endpoint 
probably never even tried to validate the token parameter.

I can see a couple of options...

1. Follow the RFC 6749 /token endpoint and return an HTTP 40X response 
with the error described in JSON in the body of the response.

2. Follow RFC 6750 and return a WWW-Authenticate Response header that 
contains the error and optionally error_description.