Re: [OAUTH-WG] Short lived access token and no refresh token
John Bradley <ve7jtb@ve7jtb.com> Tue, 25 July 2017 16:02 UTC
Return-Path: <ve7jtb@ve7jtb.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 2B129131D16 for <oauth@ietfa.amsl.com>; Tue, 25 Jul 2017 09:02:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ve7jtb-com.20150623.gappssmtp.com
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 yINAbIM4PL4C for <oauth@ietfa.amsl.com>; Tue, 25 Jul 2017 09:02:48 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 811D8126C2F for <oauth@ietf.org>; Tue, 25 Jul 2017 09:02:48 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id s6so40724807qtc.1 for <oauth@ietf.org>; Tue, 25 Jul 2017 09:02:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ve7jtb-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=y358Hs4WNjH7rLx9EAyJGR/QIZK9u+vIR769iFx/y40=; b=Klp9Z3GJ9B/Q3/JaJIglttfSmJtelheKkA7uk9XZiQ8mNAr/maa/rZWRp+WH5ulXOO 8JUxhchCUXYTp2l1LdiK9sEWFFJbDNrbTZYhFb4xEpP1Rsu6IZI8dQKJTfZXnCqkAgr1 +jIX8AY45D4iobxddxJns1a0N5njvv2U//Ehf8XNKJYkVZmYtj+xYuzCWy4ulzFeZFbk /IW2BOWxyJ2+1f/nlAAC4Xg45YIsQz8/8wknp9NITYqC8H5QtROvo2R3CaCnyeDVbJNE uvZcNKMBsFBs7NlmvXJeyrdxEAjv18FIN1abiIjrmbcK4W0Sc1rIltrboDMb4NvHkJJX dgkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=y358Hs4WNjH7rLx9EAyJGR/QIZK9u+vIR769iFx/y40=; b=XIFxJwUV/sE3RnBO3ll9+PHcBXNbN0EFW9NlwiC2f2eAEIle6g46/v+Vj0W4kVfOBR n2x8/MdCwKNQ0ra1SVFEVXYql5fkc54EsFR52RaNr1fN/HQSaT952xrctXTb+VpaHz3Y EPpcKZajWPo9um/1hgoHIs6l+UOINOTNZHAzatdZzVK8xlXl+dbW+/MHudETXU2L6oby RuRhZushCD3r6wZsW8l74scNtERP4z6cXU8CN5lC0G2RiAQJOSNS/6FFos6WOXlyXv1n ncZO53iYNCjj4uewXA2wJQrBIzxnBwo5XAf9vszwW1cyMOOxq7tublg2kBw1hsnxc9n2 BOXg==
X-Gm-Message-State: AIVw110cOpyqIRKdPHEfK2Nl+M+ZfZ+/N4iV0q2SzHINQ3GuZdT4uf49 cp9IvKXto0BSNu7D
X-Received: by 10.237.53.28 with SMTP id a28mr20731965qte.110.1500998567180; Tue, 25 Jul 2017 09:02:47 -0700 (PDT)
Received: from [192.168.86.121] ([191.115.159.202]) by smtp.gmail.com with ESMTPSA id f20sm2589163qta.58.2017.07.25.09.02.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Jul 2017 09:02:46 -0700 (PDT)
From: John Bradley <ve7jtb@ve7jtb.com>
Message-Id: <47685EB5-84E0-43FB-87CF-447C3F958588@ve7jtb.com>
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 25 Jul 2017 12:02:37 -0400
In-Reply-To: <f8d2add3-ce9a-ef3a-80cc-889f426a1b92@redhat.com>
Cc: oauth@ietf.org
To: Bill Burke <bburke@redhat.com>
References: <CAP+kwAV9pHE_3aL_-97T4-7WsP-8U=nt9J2UwdhCBhQe0x_95A@mail.gmail.com> <f8d2add3-ce9a-ef3a-80cc-889f426a1b92@redhat.com>
X-Mailer: Apple Mail (2.3273)
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="001a11c01fcc6fcab9055526766b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/ltpzxrLphLSA8xw5F3x13g2Jesk>
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 16:02:51 -0000
Max-age has to do with user re-auth in connect. Some AS only give refresh tokens if a scope of offline_acess or some such special scope is requested. There is no standard scope for that. I don’t know of any way for the client to control the lifetime of the access token other than by revoking it with the AS. https://tools.ietf.org/html/rfc7009 <https://tools.ietf.org/html/rfc7009> Depending on the AS you should be able to control the AT lifetime on a per client basis. John B. > On Jul 25, 2017, at 11:37 AM, Bill Burke <bburke@redhat.com> wrote: > > 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/ <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 <mailto:OAuth@ietf.org> >> https://www.ietf.org/mailman/listinfo/oauth <https://www.ietf.org/mailman/listinfo/oauth> > > _______________________________________________ > 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)