[Openid-specs-ab] RC1 of AB etc.

nara hideki hdknr at ic-tact.co.jp
Mon Oct 4 07:37:11 UTC 2010


Is there any reason why  "signature_string_1.signature_string_2.....
.signature_sting_n.ascii_armoured_payload" can be allowed ?

2010/10/4 nara hideki <hdknr at ic-tact.co.jp>:
> Hi Nat,
>
> This may be minor point. While "JSON Serialization" has a "signs"
> parameter holding multiple signature,  "Web Token" is a single signed
> token.
> I think we should make clearer  the difference and relation between them.
> ---
> hideki
>
> 2010/10/1 Nat Sakimura <sakimura at gmail.com>:
>> Hi All,
>> JohnB and I was working all day today to create RC1 of AB and JSON Simple
>> Sign, JSON Simple Encryption.
>> The repository is at http://bitbucket.org/openid/ab/
>> The main change for AB is that we have removed dependency on OAuth 2.0 draft
>> and Magic Signature Draft.
>> Also we have brought in JSON Simple Sign and JSON Simple Encryption in the
>> AB suite.
>> (It is in the same repository). They are used in AB, and we plan to submit
>> if for vote together with AB.
>> That way, we do not have to reference the external drafts.
>> For your convenience, I am attaching the HTML version of them here.
>> Feedback wanted.
>> --
>> Nat Sakimura (=nat)
>> http://www.sakimura.org/en/
>> http://twitter.com/_nat_en
>>
>> _______________________________________________
>> Openid-specs-ab mailing list
>> Openid-specs-ab at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-ab
>>
>>
>


More information about the Openid-specs-ab mailing list