[Specs-cx] The remaining items

[Nat Sakimura]

On Wed, Oct 26, 2011 at 4:31 AM, hideki nara <hdknr at ic-tact.co.jp> wrote:

> Topics can be the followings:
>
>  - Multiple tokens for a single Connect session :  may be covered in "to
> define the claims structure only".
>

Is it not covered by the distributed claim response of UserInfo endpoint?


>  - Token validation by  the Protected Resources other than OAuth Servers :
> UMA may cover this.
>

Probably yes. It should leverage on JWT and asymmetric crypto.


>  - Delegations(?) ( Delivering access tokens to Clients other than RP which
> initiates a Connect session )
>

Asymmetrically encrypted access token, I suppose.
Need to define them. I guess UMA would also need it.


>  - Notification..
>
> Any others ?
>

I think these requirements cover pretty well.

> --
> hdknr
>
> 2011/10/22 Nat Sakimura <sakimura at gmail.com>
>
>> So, much of the earlier Contract Exchange work (underlying protocol) were
>> taken up by the new Connect protocol.
>> This means that the remaining bit of things that this working group has to
>> do is to define the claims structure only, which is good.
>> In the past, we have been talking about it in XML but as Connect is
>> completely JSON based, perhaps we should try to convert it to JSON as well.
>>
>> It should not be too difficult to do.
>>
>> Also, there are related protocols like open-transact being proposed
>> elsewhere. Perhaps we shall look at it as well.
>>
>> Thoughts?
>>
>> --
>> Nat Sakimura (=nat)
>> Chairman, OpenID Foundation
>> http://nat.sakimura.org/
>> @_nat_en
>>
>>
>> _______________________________________________
>> Specs-cx mailing list
>> Specs-cx at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-cx
>>
>>
>


-- 
Nat Sakimura (=nat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-cx/attachments/20111026/e7e0231c/attachment.html>