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

Prabath Siriwardena <prabath@wso2.com> Thu, 07 February 2013 16:26 UTC

Return-Path: <prabath@wso2.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 4D78F21F842D for <oauth@ietfa.amsl.com>; Thu, 7 Feb 2013 08:26:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.823
X-Spam-Level:
X-Spam-Status: No, score=-2.823 tagged_above=-999 required=5 tests=[AWL=0.153, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GMsHdUgBvhu1 for <oauth@ietfa.amsl.com>; Thu, 7 Feb 2013 08:26:30 -0800 (PST)
Received: from mail-ee0-f50.google.com (mail-ee0-f50.google.com [74.125.83.50]) by ietfa.amsl.com (Postfix) with ESMTP id DAF8121F81FF for <oauth@ietf.org>; Thu, 7 Feb 2013 08:26:29 -0800 (PST)
Received: by mail-ee0-f50.google.com with SMTP id e51so1525136eek.23 for <oauth@ietf.org>; Thu, 07 Feb 2013 08:26:29 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=wXD/BolpUDUFKFZHli94v9GyyW6+VGdfjxFWfEZUIRU=; b=ggv4HxuGpE4HtmW1Yw30SU+HMGuMlbTQuRGlyLgvqyA1DD/EjP1fA6wNDVKfT5Jijo u3GkTjs30uNFRZPMFEuRAejjX7skCaRPAfLxAYXhkQjRbWhxPeFCHk7/bIEqB3gtztqL /UIgO4goN0SnmzNRQezwYjgHsE7xAl02BHm8bkHGHDmPd99do0BsTsRVjkErv2WBbx9o Pqgm8oi8MyH2GEnZpOXwvKpRbiO4SbCRkMRpRUzdqdI55qxGKOaK6pawn0TjNcVmmeAE 8bDhP0pzKIiby1j/ZmBofDdIXM3m/e43skP7ssHHa5O5wbGA61iJrYy6vlq8dYftF1Zv Xh0w==
MIME-Version: 1.0
X-Received: by 10.14.194.195 with SMTP id m43mr5409058een.44.1360254388588; Thu, 07 Feb 2013 08:26:28 -0800 (PST)
Received: by 10.223.175.134 with HTTP; Thu, 7 Feb 2013 08:26:28 -0800 (PST)
In-Reply-To: <5113C3AA.1040701@mitre.org>
References: <20130206192420.32698.21027.idtracker@ietfa.amsl.com> <5112AE0B.1080501@mitre.org> <CAJV9qO_8-4FowrXK=ae-+xMjiJFP04ryVMLQ8SGUH8kp3PHrLg@mail.gmail.com> <5113C3AA.1040701@mitre.org>
Date: Thu, 07 Feb 2013 21:56:28 +0530
Message-ID: <CAJV9qO8BVV57eAb5kUNes15AYOpUKqw5XWQswh-FJA=b1pPgSA@mail.gmail.com>
From: Prabath Siriwardena <prabath@wso2.com>
To: Justin Richer <jricher@mitre.org>
Content-Type: multipart/alternative; boundary="047d7b342c4ca2d27b04d524e790"
X-Gm-Message-State: ALoCoQmtJDCEY0gxu6NAiKjg/2FxsP7TcUGKulxAmK4LrjX3yG92g94APqKK6h/OTwFhpk1QttX5
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Fwd: New Version Notification for draft-richer-oauth-introspection-02.txt
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 07 Feb 2013 16:26:31 -0000

Okay.. I was thinking this could be used as a way to validate the token as
well. BTW even in this case shouldn't communicate the type of token to AS?
For example in the case of SAML profile - it could be SAML token..

Thanks & regards,
-Prabath

On Thu, Feb 7, 2013 at 8:39 PM, Justin Richer <jricher@mitre.org> wrote:

>  "valid" might not be the best term, but it's meant to be a field where
> the server says "yes this token is still good" or "no this token isn't good
> anymore". We could instead do this with HTTP codes or something but I went
> with a pure JSON response.
>
>  -- Justin
>
>
> On 02/06/2013 10:47 PM, Prabath Siriwardena wrote:
>
> Hi Justin,
>
>  I believe this is addressing one of the key missing part in OAuth 2.0...
>
>  One question - I guess this was discussed already...
>
>  In the spec - in the introspection response it has the attribute "valid"
> - this is basically the validity of the token provided in the request.
>
>  Validation criteria depends on the token and well as token type (
> Bearer, MAC..).
>
>  In the spec it seems like it's coupled with Bearer token type... But I
> guess, by adding "token_type" to the request we can remove this dependency.
>
>  WDYT..?
>
>  Thanks & regards,
> -Prabath
>
> On Thu, Feb 7, 2013 at 12:54 AM, Justin Richer <jricher@mitre.org> wrote:
>
>>  Updated introspection draft based on recent comments. Changes include:
>>
>>  - "scope" return parameter now follows RFC6749 format instead of JSON
>> array
>>  - "subject" -> "sub", and "audience" -> "aud", to be parallel with JWT
>> claims
>>  - clarified what happens if the authentication is bad
>>
>>  -- Justin
>>
>>
>> -------- Original Message --------  Subject: New Version Notification
>> for draft-richer-oauth-introspection-02.txt  Date: Wed, 6 Feb 2013
>> 11:24:20 -0800  From: <internet-drafts@ietf.org><internet-drafts@ietf.org>  To:
>> <jricher@mitre.org> <jricher@mitre.org>
>>
>> A new version of I-D, draft-richer-oauth-introspection-02.txt
>> has been successfully submitted by Justin Richer and posted to the
>> IETF repository.
>>
>> Filename:	 draft-richer-oauth-introspection
>> Revision:	 02
>> Title:		 OAuth Token Introspection
>> Creation date:	 2013-02-06
>> WG ID:		 Individual Submission
>> Number of pages: 6
>> URL:             http://www.ietf.org/internet-drafts/draft-richer-oauth-introspection-02.txt
>> Status:          http://datatracker.ietf.org/doc/draft-richer-oauth-introspection
>> Htmlized:        http://tools.ietf.org/html/draft-richer-oauth-introspection-02
>> Diff:            http://www.ietf.org/rfcdiff?url2=draft-richer-oauth-introspection-02
>>
>> Abstract:
>>    This specification defines a method for a client or protected
>>    resource to query an OAuth authorization server to determine meta-
>>    information about an OAuth token.
>>
>>
>>
>>
>>
>> The IETF Secretariat
>>
>>
>>
>>
>>
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>>
>>
>
>
>  --
> Thanks & Regards,
> Prabath
>
>  Mobile : +94 71 809 6732
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
>
>
>


-- 
Thanks & Regards,
Prabath

Mobile : +94 71 809 6732

http://blog.facilelogin.com
http://RampartFAQ.com