Hi,
On 03/01/13 22:45, Justin Richer wrote:
I'd like to present two use cases for signed tokens, for input into the
ongoing MAC/HoK/higher-security discussion. Both of these are actual
cases that I've done in the past, and we've used either OAuth 1 or JW*
to solve them. I think that with the righ
Hi Justin,
see below.
On Jan 11, 2013, at 4:34 PM, Richer, Justin P. wrote:
> Hannes, thanks for the input. Inline:
>
> On Jan 11, 2013, at 4:33 AM, Hannes Tschofenig
> wrote:
>
>> Hi Justin,
>>
>> thanks for the input.
>>
>> A few minor remarks inside:
>>
>> On Jan 4, 2013, at 12:45 A
Hannes, thanks for the input. Inline:
On Jan 11, 2013, at 4:33 AM, Hannes Tschofenig
wrote:
> Hi Justin,
>
> thanks for the input.
>
> A few minor remarks inside:
>
> On Jan 4, 2013, at 12:45 AM, Justin Richer wrote:
>
>> I'd like to present two use cases for signed tokens, for input into
Hi Justin,
thanks for the input.
A few minor remarks inside:
On Jan 4, 2013, at 12:45 AM, Justin Richer wrote:
> I'd like to present two use cases for signed tokens, for input into the
> ongoing MAC/HoK/higher-security discussion. Both of these are actual cases
> that I've done in the past,
I'd like to present two use cases for signed tokens, for input into the
ongoing MAC/HoK/higher-security discussion. Both of these are actual
cases that I've done in the past, and we've used either OAuth 1 or JW*
to solve them. I think that with the right tooling, a MAC-token-like
thing could be
