[OAUTH-WG] Short lived access token and no refresh token
Saurav Sarkar <saurav.sarkar1@gmail.com> Tue, 25 July 2017 14:48 UTC
Return-Path: <saurav.sarkar1@gmail.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 85D6D1317B1 for <oauth@ietfa.amsl.com>; Tue, 25 Jul 2017 07:48:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=gmail.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 19iAfgA0_ToJ for <oauth@ietfa.amsl.com>; Tue, 25 Jul 2017 07:48:18 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (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 037A91270B4 for <oauth@ietf.org>; Tue, 25 Jul 2017 07:48:18 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id x3so50393260oia.1 for <oauth@ietf.org>; Tue, 25 Jul 2017 07:48:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=0B1vWG0bqaVs7zGZF7C7GGgOSOWbYy7+9jSkgqcmmEQ=; b=UTGxu9j29r7oESh+hWIIIZ9rJDeuF55dfvqKvbrycGoa8NfngZ043tB6B9M2Uw8Qzj McuR8C7qbtjkd8Elu4QX3fCscnmil2ppvg2mDP2KdR3Ar0B8ehITie6ctmB6b/6waoKg deiw6N4dejoKo01CyrsbhDVlpl6SD4zvWHlr82c+DmwdzxnSb85dX2G/eH1OmQPFHi1w SOgzllRnj3g/eBmkJOaHv8kIiU+0qyh2oxXvBIIr5bCyeCWIwNLB22HloOdlxFm92znM fDJg1OrG9ugeoazZ/PTuPYRV4VWgZ4kSEVOmpKk3Jf8yQp+0MeoJxebte7ewHXuVSGlz G1YA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=0B1vWG0bqaVs7zGZF7C7GGgOSOWbYy7+9jSkgqcmmEQ=; b=XvfJFBmb0xbvuF2aJfCDAqAxXD8iRHWNT7IUHV9+5mEpdihGU/DQ42heyo8XJYhipZ i1p03iFT6oQIm+NljP1st7xKCLBSC+VSFf3ZyXRnWLVC6QhVkJhas8NG4ktQmU8bQ3yN ITI71c5bO/b0BKMNHYNXAgHhUgz8UClLpNdxeA29xWPMhxCbgdpHQAngWvOd0dVds0wt zLYDOOTtV/PsXhplyth/tj5EIYHyA4EysABVzbg0djeY7g+5x4p9fYM1NXj3krB6ayx5 qZxkLYeu8rCNuOnofgNip0vHA52H7WoCV6H0TLKxvk63agCBuzAYs4hXl2dIl7ioFL/d 8Mxg==
X-Gm-Message-State: AIVw111i/arZS2jlLJnE/d93tKQtJtrqRF7WDlxxesMaupXptlx8p24S BbVKnlBce0Q1pQo81GdqCzmujLrMqwzh
X-Received: by 10.202.227.5 with SMTP id a5mr8500238oih.240.1500994097152; Tue, 25 Jul 2017 07:48:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.0.199 with HTTP; Tue, 25 Jul 2017 07:48:16 -0700 (PDT)
From: Saurav Sarkar <saurav.sarkar1@gmail.com>
Date: Tue, 25 Jul 2017 20:18:16 +0530
Message-ID: <CAP+kwAV9pHE_3aL_-97T4-7WsP-8U=nt9J2UwdhCBhQe0x_95A@mail.gmail.com>
To: oauth@ietf.org
Content-Type: multipart/alternative; boundary="001a1141a572f889600555256b1a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/5s065NysglulF-rXvcHqgg25saU>
Subject: [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 14:49:11 -0000
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-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)