Re: [jose] JOSE implementation Interoperability events

Sergey Beryozkin <sberyozkin@gmail.com> Thu, 26 May 2016 16:57 UTC

Return-Path: <sberyozkin@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8011A12B043 for <jose@ietfa.amsl.com>; Thu, 26 May 2016 09:57:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 CN0bWKu1kFQB for <jose@ietfa.amsl.com>; Thu, 26 May 2016 09:57:40 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::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 C7A8412D7B1 for <jose@ietf.org>; Thu, 26 May 2016 09:57:29 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id n129so236450771wmn.1 for <jose@ietf.org>; Thu, 26 May 2016 09:57:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=NEErkC0lLmOGkp8Y8z1K/60Fv1fYIRz7I54PmtDI28I=; b=O4H+/mGe+zwUzhiEGubhw0JULU+EokfYghoW0IKgBhYkS0yLrT83jftkPE+I4H4Y4o 7TRypNHJdFIrORtJ1wEcHOHxVdBgrRsOvTzqkhN9+W9+JiFWRft8IvSOoMXvRJSJ9ZVc Casw+PT1JRVzcBpoTfAiNMZuV323shUQ80Ig6FbgEblGozPLzJrfgocLlB7ACW/cGHWw kD+/osmVKfmWnXg/DqD2gR1z+6g5H9lipSYBiCiD65zqe1JJ/Op0s+gHh1kn8PghMkeq 1u6TMIafbvwDjhr1zc7QdEG9wGdGmgV2WBt5SAMXDwDH1B1c7EApiw64GAbPs2j+z/oo gATw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=NEErkC0lLmOGkp8Y8z1K/60Fv1fYIRz7I54PmtDI28I=; b=EPweWFSq4EW9zgrH1Kmz2MronRC9R3t3MNrnrZoU77BxwawQQy7AREd+A/y4ZOXIl/ Og7RXUc+2GsxQkhRNDcWApxqAjzepHlNcl78XYGZx+hJ0SrUY3u8QeME6jtgU+J3DAuI a+S7NTRcYp6go6NcTakQOumUTdnOa4s0mXGkANOqpGaK57m7W0dZTa8husiYQ/nmEfgB coioDS4rKBigoAOHdzAISTwZTOTW6Zi08llc7A6b8cDmw+eFTix30ZbV6sNTiI13mc7R jRUNUWirz5dzRE1exyj4dty1q11kwwJoi9MIHIvSWw67mvYiPqQau8/+O0V09s4J6vYV e5gA==
X-Gm-Message-State: ALyK8tIyGBGk+Mo/dxKqLtJt8V1pE/BrUoUmQgs4IzIlJojQRVg2bZkSnk3liTd0hwog8g==
X-Received: by 10.28.181.148 with SMTP id e142mr4527308wmf.38.1464281848299; Thu, 26 May 2016 09:57:28 -0700 (PDT)
Received: from [10.36.226.98] ([80.169.137.53]) by smtp.googlemail.com with ESMTPSA id d5sm15189742wje.20.2016.05.26.09.57.27 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 26 May 2016 09:57:27 -0700 (PDT)
To: Anders Rundgren <anders.rundgren.net@gmail.com>, Jim Schaad <ietf@augustcellars.com>, jose@ietf.org
References: <57446515.8070900@gmail.com> <5746C234.6010109@gmail.com> <03a201d1b769$acf63240$06e296c0$@augustcellars.com> <89365079-1afd-d20b-d5bc-a67097135237@gmail.com>
From: Sergey Beryozkin <sberyozkin@gmail.com>
Message-ID: <57472AF6.4080107@gmail.com>
Date: Thu, 26 May 2016 17:57:26 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <89365079-1afd-d20b-d5bc-a67097135237@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/jose/w50ksdZoYGNGmGFdiKMTCTAtaL0>
Subject: Re: [jose] JOSE implementation Interoperability events
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose/>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 16:57:42 -0000

Hi Jim, Anders

I was just planning to clarify where my interest was coming from :-),

I'd like to see more JWS/JWE sequences flowing between regular client 
and server applications which are not necessarily OAuth2 applications.

For example, I'd like to see a "Hello World" client written in C# 
posting a JOSE secured "HelloWorld" sequence to a Java server which 
processes it and makes the original "HelloWorld" available to the server.

But I'm sure the situations exist or will exist where OAuth2 clients and 
OIDC servers use/will use different JOSE libraries for 
signing/validating id tokens, etc.

So having some standard interoperability system where some text is 
submitted into a given library, the output is accepted by another 
library, and then somehow it is asserted that the 2nd library did not do 
a false positive validation, and that it correctly reproduced the 
encrypted text, can be useful.

But I guess it can be hard to set up.
If such an interoperability event can be set up then I'll be interested 
in attending, though in a more distant future, I'm not sure when the 
next Hackathon is but looks like it is coming soon :-)

Thanks, Sergey

On 26/05/16 17:31, Anders Rundgren wrote:
> On 2016-05-26 18:14, Jim Schaad wrote:
>> Are people interested in doing anything along these lines at the next
>> IETF
>> meeting as part of the hackathon?  If so then I can set it up.
>
> What kind of interoperability testing are you looking for?
> I'm sure just about every JSON parser out there manages parsing
> legitimate JSON data.
>
> What has recently been identified as "differing" (not necessarily the
> same as
> non-conformant), are things like case sensitivity (missing in GO), quite
> different ways of serializing floating point numbers (Python), and of
> course
> my personal favorite; the ability honoring property order during parsing
> and serialization where the ES6 folks took the lead (albeit with a little
> twist for fully numeric property names).
>
> Anders
>
>>
>> Jim
>>
>>
>>> -----Original Message-----
>>> From: jose [mailto:jose-bounces@ietf.org] On Behalf Of Sergey Beryozkin
>>> Sent: Thursday, May 26, 2016 2:30 AM
>>> To: jose@ietf.org
>>> Subject: [jose] JOSE implementation Interoperability events
>>>
>>> Hi All
>>>
>>> Are there any interoperability events scheduled in the near future where
>> the
>>> various implementations can be tested ?
>>>
>>> Thanks, Sergey
>>>
>>> _______________________________________________
>>> jose mailing list
>>> jose@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jose
>>
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>>
>


-- 
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/