Re: [OAUTH-WG] in-app logout?

Dick Hardt <dick.hardt@gmail.com> Mon, 17 May 2010 00:27 UTC

DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=F2yZR+PgNzybkHLns29xnk67JMP07ncDtxuwWe2EY2LYrf0+raYh1Mw8TwlIPhmPQ0 47V19lN3jjRiizxifjSP5NSj1o3VVgi/XuCRV/lLmxSvjPD5oz0zo9hd+xICpF52kkUM dD9/wb67Uz2+NfvMf7kafl5NFCyfY4YMFUUhc=
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
From: Dick Hardt <dick.hardt@gmail.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E112634F5EA3@WSMSG3153V.srv.dir.telstra.com>
Date: Sun, 16 May 2010 17:26:48 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7934BAC5-7FA8-48E7-82A5-A4A17DE9146E@gmail.com>
References: <4BEBDCFB.7090503@lodderstedt.net> <255B9BB34FB7D647A506DC292726F6E11263465727@WSMSG3153V.srv.dir.telstra.com> <AANLkTikxD3jraqvG2IFmaSme0f1Q7NGPuQ3llqX3Ds5W@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E112634F5EA3@WSMSG3153V.srv.dir.telstra.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Cc: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] in-app logout?
Precedence: list

On 2010-05-16, at 5:20 PM, Manger, James H wrote:

> Dick,
> 
>> James: An important capability of the refresh token is that it *can* be a self contained token in that is not an id, but a signed token that can be examined and acted upon on presentation.
> 
> Defining refresh_token as a URI does not prevent it being a self-contained signed token.
> 
> The only limitation implied is a URI size limit. A few KB, however, is not that onerous a limit -- it is sufficient to hold a 4096-bit RSA signature with a couple of KB over for permissions etc.).

Agreed, a token could be a self contained token. A design objective was allowing existing systems to use existing tokens.

-- Dick

[OAUTH-WG] in-app logout? Torsten Lodderstedt
Re: [OAUTH-WG] in-app logout? Manger, James H
Re: [OAUTH-WG] in-app logout? Dick Hardt
Re: [OAUTH-WG] in-app logout? Manger, James H
Re: [OAUTH-WG] in-app logout? Dick Hardt
Re: [OAUTH-WG] in-app logout? Yaron Goland
Re: [OAUTH-WG] in-app logout? Manger, James H
Re: [OAUTH-WG] in-app logout? Manger, James H
Re: [OAUTH-WG] in-app logout? Chasen Le Hara
Re: [OAUTH-WG] in-app logout? Hubert Le Van Gong
Re: [OAUTH-WG] in-app logout? Allen Tom
Re: [OAUTH-WG] in-app logout? Lukas Rosenstock
Re: [OAUTH-WG] in-app logout? Beau Lebens
Re: [OAUTH-WG] in-app logout? Hubert Le Van Gong
Re: [OAUTH-WG] in-app logout? Torsten Lodderstedt
Re: [OAUTH-WG] in-app logout? Igor Faynberg
Re: [OAUTH-WG] in-app logout? Eran Hammer-Lahav
Re: [OAUTH-WG] in-app logout? Torsten Lodderstedt
Re: [OAUTH-WG] in-app logout? Eran Hammer-Lahav
Re: [OAUTH-WG] in-app logout? Manger, James H
Re: [OAUTH-WG] in-app logout? Justin Richer
[OAUTH-WG] Fwd: Re: in-app logout? Torsten Lodderstedt
Re: [OAUTH-WG] in-app logout? Eran Hammer-Lahav
Re: [OAUTH-WG] Fwd: Re: in-app logout? Justin Richer
Re: [OAUTH-WG] Fwd: Re: in-app logout? George Fletcher