[OAUTH-WG] Fwd: [oauth-interop] scope and reach of testing activity
Prateek Mishra <prateek.mishra@oracle.com> Mon, 07 October 2013 21:39 UTC
Return-Path: <prateek.mishra@oracle.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 D862011E813A for <oauth@ietfa.amsl.com>; Mon, 7 Oct 2013 14:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id leYtvyP2i0hR for <oauth@ietfa.amsl.com>; Mon, 7 Oct 2013 14:39:03 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 5E54B11E813D for <oauth@ietf.org>; Mon, 7 Oct 2013 14:39:00 -0700 (PDT)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r97LcxQw019528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <oauth@ietf.org>; Mon, 7 Oct 2013 21:39:00 GMT
Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r97Lcwow018583 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <oauth@ietf.org>; Mon, 7 Oct 2013 21:38:59 GMT
Received: from abhmt106.oracle.com (abhmt106.oracle.com [141.146.116.58]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r97LcwRp006598 for <oauth@ietf.org>; Mon, 7 Oct 2013 21:38:58 GMT
Received: from [130.35.50.182] (/130.35.50.182) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 07 Oct 2013 14:38:58 -0700
Message-ID: <525329EE.5040403@oracle.com>
Date: Mon, 07 Oct 2013 14:38:54 -0700
From: Prateek Mishra <prateek.mishra@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130911 Thunderbird/17.0.9
MIME-Version: 1.0
To: IETF oauth WG <oauth@ietf.org>
References: <524F53E2.6050901@oracle.com>
In-Reply-To: <524F53E2.6050901@oracle.com>
X-Forwarded-Message-Id: <524F53E2.6050901@oracle.com>
Content-Type: multipart/alternative; boundary="------------040601030902030509020000"
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Subject: [OAUTH-WG] Fwd: [oauth-interop] scope and reach of testing activity
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: Mon, 07 Oct 2013 21:39:09 -0000
Folks interested in OAuth interop/implementation testing may want to participate in this discussion. Details at: http://www.ietf.org/mail-archive/web/oauth/current/msg12128.html -------- Original Message -------- Subject: [oauth-interop] scope and reach of testing activity Date: Fri, 04 Oct 2013 16:48:50 -0700 From: Prateek Mishra <prateek.mishra@oracle.com> Organization: Oracle Corporation To: oauth-interop@elists.isoc.org Hello OAuth Interop list, I would be interested in kicking off a discussion around the definition of scope and reach of the proposed testing activity. OAuth interop, of course, is the core activity. I assume this would take the form of testing the exchanges described in Sections 4-6 of RFC 6749 for each of the different client and grant types. Both positive and negative tests would presumably be included. But OAuth is also a security specification, and there are constraints defined over OAuth server and client behavior with respect to redirect_uri checking, access code and token lifetimes and so on. In addition to the material in Sections 4-6, there are additional constraints described in Section 10 and, of course, RFC 6819. So thats another area that would benefit from a set of tests, but I can see that describing these tests might be more challenging. I would be interested in other opinions on the scope and nature of tests being developed by this group. - prateek _______________________________________________ Oauth-interop mailing list Oauth-interop@elists.isoc.org https://elists.isoc.org/mailman/listinfo/oauth-interop
- [OAUTH-WG] Fwd: [oauth-interop] scope and reach o… Prateek Mishra
- Re: [OAUTH-WG] Fwd: [oauth-interop] scope and rea… Anthony Nadalin
- Re: [OAUTH-WG] Fwd: [oauth-interop] scope and rea… Mike Jones
- Re: [OAUTH-WG] Fwd: [oauth-interop] scope and rea… Prateek Mishra
- Re: [OAUTH-WG] Fwd: [oauth-interop] scope and rea… Mike Jones
- Re: [OAUTH-WG] Fwd: [oauth-interop] scope and rea… John Bradley