Re: [OAUTH-WG] Short lived access token and no refresh token
Bill Burke <bburke@redhat.com> Tue, 25 July 2017 15:38 UTC
Return-Path: <bburke@redhat.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78E09131D0F for <oauth@ietfa.amsl.com>; Tue, 25 Jul 2017 08:38:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 yyUd0aN6Uoi7 for <oauth@ietfa.amsl.com>; Tue, 25 Jul 2017 08:38:45 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F64E131C3A for <oauth@ietf.org>; Tue, 25 Jul 2017 08:38:45 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 39451A037E for <oauth@ietf.org>; Tue, 25 Jul 2017 15:38:45 +0000 (UTC)
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 39451A037E
Authentication-Results: ext-mx10.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-Results: ext-mx10.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=bburke@redhat.com
Received: from ovpn-116-67.phx2.redhat.com (ovpn-116-67.phx2.redhat.com [10.3.116.67]) by smtp.corp.redhat.com (Postfix) with ESMTP id DBEFF953AA for <oauth@ietf.org>; Tue, 25 Jul 2017 15:38:31 +0000 (UTC)
To: oauth@ietf.org
References: <CAP+kwAV9pHE_3aL_-97T4-7WsP-8U=nt9J2UwdhCBhQe0x_95A@mail.gmail.com>
From: Bill Burke <bburke@redhat.com>
Message-ID: <f8d2add3-ce9a-ef3a-80cc-889f426a1b92@redhat.com>
Date: Tue, 25 Jul 2017 11:37:54 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAP+kwAV9pHE_3aL_-97T4-7WsP-8U=nt9J2UwdhCBhQe0x_95A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------303B66D9B24CC4787F24FE0E"
Content-Language: en-US
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Tue, 25 Jul 2017 15:38:45 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/UQHeJa0rqUcY_phQKMj5ZFvmqr0>
Subject: Re: [OAUTH-WG] Short lived access token and no refresh token
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2017 15:38:47 -0000
For browser apps, implicit flow provides an access token but no refresh token. For non-browser apps only client credentials grant doesn't supply a refresh token. As for token access times, I believe only extensions to OAuth define those types of capabilities. i.e. OpenID Connect defines a "max-age" claim that you can pass when requesting a token. On 7/25/17 10:48 AM, Saurav Sarkar wrote: > Hi All, > > We have a scenario where one of our stakeholder wants to mandatorily > initiate the authentication at certain point of time. > > As per > https://www.oauth.com/oauth2-servers/access-tokens/access-token-lifetime/ > there can be an option where access token is set for certain time and > refresh token is not set. So we want to explore this option for this > scenario. > > I have couple of questions regarding this > > (a) Is this option part of OAuth 2 specification ? If yes can you > please point me to the exact IETF link ? > > (b) Is there any other way our scenario can be achieved ? We want this > scenario to be supported from the authorization server (platform) > itself and not in the client app or resource server. > > Thanks and Best Regards, > Saurav > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] Short lived access token and no refres… Saurav Sarkar
- Re: [OAUTH-WG] Short lived access token and no re… Bill Burke
- Re: [OAUTH-WG] Short lived access token and no re… John Bradley
- Re: [OAUTH-WG] Short lived access token and no re… CARLIER Bertrand
- Re: [OAUTH-WG] Short lived access token and no re… Phil Hunt (IDM)