Re: [sipcore] token-authnz: Access Token and Refresh Token
"Olle E. Johansson" <oej@edvina.net> Mon, 15 July 2019 07:50 UTC
Return-Path: <oej@edvina.net>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB87120074 for <sipcore@ietfa.amsl.com>; Mon, 15 Jul 2019 00:50:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 cLHcydNmwLQa for <sipcore@ietfa.amsl.com>; Mon, 15 Jul 2019 00:50:32 -0700 (PDT)
Received: from smtp7.webway.se (smtp7.webway.se [212.3.14.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A96512001E for <sipcore@ietf.org>; Mon, 15 Jul 2019 00:50:31 -0700 (PDT)
Received: from haworthia-20.webway.org (h-205-16.A165.corp.bahnhof.se [176.10.205.16]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp7.webway.se (Postfix) with ESMTPSA id 8841FA40; Mon, 15 Jul 2019 09:50:27 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: "Olle E. Johansson" <oej@edvina.net>
In-Reply-To: <C3CBEDCA-A2B9-4F1C-B45A-873289AD53EC@ericsson.com>
Date: Mon, 15 Jul 2019 09:50:26 +0200
Cc: Olle E Johansson <oej@edvina.net>, "sipcore@ietf.org" <sipcore@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CB3A6B91-CDCB-4098-97B8-526727307E70@edvina.net>
References: <C3CBEDCA-A2B9-4F1C-B45A-873289AD53EC@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/QhKPZPjLQDaC47BnWLzM1JCFxbw>
Subject: Re: [sipcore] token-authnz: Access Token and Refresh Token
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jul 2019 07:50:35 -0000
> On 12 Jul 2019, at 15:26, Christer Holmberg <christer.holmberg@ericsson.com> wrote: > > Hi, > > When scanning through the e-mails, I realized one thing: we have been talking about OAuth Access Tokens and Refresh Tokens. > > However, only Access Tokens will be transported in SIP. Refresh Tokens are only between the SIP UA and the Authorization Server, and that interface is outside of the scope of the document. > Correct, we only need access tokens and in the case of OpenID connect the identity tokens. /O
- [sipcore] token-authnz: Access Token and Refresh … Christer Holmberg
- Re: [sipcore] token-authnz: Access Token and Refr… Olle E. Johansson