[OAUTH-WG] draft-ietf-oauth-security-topics: Migration strategies for deprecated password grant

Jorge Bernal <jorge@automattic.com> Wed, 27 November 2019 14:53 UTC

Return-Path: <jorge@automattic.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 44F86120964 for <oauth@ietfa.amsl.com>; Wed, 27 Nov 2019 06:53:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=automattic.com header.b=sFkbZuV5; dkim=pass (1024-bit key) header.d=automattic.com header.b=sFkbZuV5
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 UwvzRWANA6W8 for <oauth@ietfa.amsl.com>; Wed, 27 Nov 2019 06:53:43 -0800 (PST)
Received: from smtp1.lax.automattic.com (mail.automattic.com [192.0.64.46]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3834D120926 for <oauth@ietf.org>; Wed, 27 Nov 2019 06:53:43 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp1.lax.automattic.com (Postfix) with ESMTP id 036D718E1315 for <oauth@ietf.org>; Wed, 27 Nov 2019 14:53:43 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at wordpress.com
Received: from smtp1.lax.automattic.com ([127.0.0.1]) by localhost (smtp1.lax.automattic.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jjri-LHzmrde for <oauth@ietf.org>; Wed, 27 Nov 2019 14:53:37 +0000 (UTC)
Received: from smtp-gw2.automattic.com (smtp-gw2.automattic.com [192.0.65.221]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp1.lax.automattic.com (Postfix) with ESMTPS id E716E18E140E for <oauth@ietf.org>; Wed, 27 Nov 2019 14:53:37 +0000 (UTC)
Received: from smtp-gw2.automattic.com (localhost.localdomain [127.0.0.1]) by smtp-gw2.automattic.com (Postfix) with ESMTP id D2594204FA for <oauth@ietf.org>; Wed, 27 Nov 2019 14:53:37 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=automattic.com; s=my5; t=1574866417; bh=L9bZkdOhskIZZbwvrZzfMjjAs848mfL8sNdkEfK1fR0=; h=From:Subject:Date:To:From; b=sFkbZuV5lHNa4stIUiEi3Mnf9ygYuWe8pkbLpLkjBtcBEvKugr8TbwaGteEX1ECGT tINd5BlEHFhVt+0szGR8QZbADbYGLugmn3HvXgiUTSziYBRyiXEm4RQq1OYb9I1Ux7 EKyujav5cEi3cf/dw5fGc6tGXyO9GRUJY18ahJzw=
Received: from mail-wr1-f72.google.com (mail-wr1-f72.google.com [209.85.221.72]) by smtp-gw2.automattic.com (Postfix) with ESMTP id 7EE492044E for <oauth@ietf.org>; Wed, 27 Nov 2019 14:53:37 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=automattic.com; s=my5; t=1574866417; bh=L9bZkdOhskIZZbwvrZzfMjjAs848mfL8sNdkEfK1fR0=; h=From:Subject:Date:To:From; b=sFkbZuV5lHNa4stIUiEi3Mnf9ygYuWe8pkbLpLkjBtcBEvKugr8TbwaGteEX1ECGT tINd5BlEHFhVt+0szGR8QZbADbYGLugmn3HvXgiUTSziYBRyiXEm4RQq1OYb9I1Ux7 EKyujav5cEi3cf/dw5fGc6tGXyO9GRUJY18ahJzw=
Received: by mail-wr1-f72.google.com with SMTP id d8so8333148wrq.12 for <oauth@ietf.org>; Wed, 27 Nov 2019 06:53:37 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=kucHtLxwyG8JlYZXJtSQqyJBaTiLb2JH8qaUW3nwQ0c=; b=d2Km2Ze+w8CnYC6BxbrM7AUFCUuWQ4XgN798iz/DEEJm68PMUU70RaBmUlm1+lIU4K tp7ZmLqzTcABHjtpthU52T86s7AmyU1J5wvOw+qAUEqzUKfKK01Vpee8hvny2jxow5N+ SmegoRVVfXUMihDRkyARhbR8SpZW98xCcMSxTiL6tBm3P/GAnANdKRTHwkXtpt+pDgA6 KfLkkHCRbH+BiMRr8Z/ZjisfQKzqguM9vc18FQ1HB/BWr3WRwQ0hDd/VuMzT2xDAAONk vyUKDrvMxwkQHNe1dh9lDLxaRD5+VbcHQWcZaj0WMdZW+M0OUCx9FAQf33H/IxbmRss0 KGTA==
X-Gm-Message-State: APjAAAW9+D0MTh2mJHedyVFDwuapXzrOcEMh1Sgm0pvja2/Gk+JA5odV +JjbpIP36c7QgD24cYc6SqG0jwzfkRPuo2m/+nvUwuNMOjwLpWClAsQ+vyIuJPKVxHNxNo61jZt ziQKUVFre9Ej6CvsikNhNxQ==
X-Received: by 2002:adf:ec8f:: with SMTP id z15mr25708712wrn.128.1574866416281; Wed, 27 Nov 2019 06:53:36 -0800 (PST)
X-Google-Smtp-Source: APXvYqzQBfPAlgGBeFPIZMXWK2Kdk8ufC6Lg9PR8l5aGjN/sswlALCkqqjJA4apeDxruxT93mDNfiw==
X-Received: by 2002:adf:ec8f:: with SMTP id z15mr25708692wrn.128.1574866415938; Wed, 27 Nov 2019 06:53:35 -0800 (PST)
Received: from [192.168.1.12] (36.red-193-153-135.dynamicip.rima-tde.net. [193.153.135.36]) by smtp.gmail.com with ESMTPSA id a2sm20111979wrt.79.2019.11.27.06.53.34 for <oauth@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Nov 2019 06:53:35 -0800 (PST)
From: Jorge Bernal <jorge@automattic.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Message-Id: <3A49525F-7E00-477E-9090-F247785B9E97@automattic.com>
Date: Wed, 27 Nov 2019 15:53:32 +0100
To: oauth@ietf.org
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/-HIQYdle2wmL5_DoPh5c-245-mE>
Subject: [OAUTH-WG] draft-ietf-oauth-security-topics: Migration strategies for deprecated password grant
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 28 Nov 2019 09:33:26 -0000

Hi all,

We are currently discussing[1] an implementation of oAuth for WordPress and
what this would mean for our mobile apps[2].

It was noted that the new recommendation will completely discourage the use of
the password grant. While I agree in principle that this is a good thing
overall, we will have to find a migration path. 

Going through meeting minutes[3] I noticed this was already in your radar, but
I haven’t been able to find any further mention:

> Need to provide alternatives to lots of folks using this grant

As I mention on our discussion, our reality is that we have thousands of
existing users for whom we only have passwords, and we would need a migration
path to obtain tokens for those users. Without the password grant, I don’t see
a clear way to do that without asking users to log in again.

Besides that, I expect a transitional period where we will also need to keep
the user’s password to be able to interact with legacy APIs that don’t support
the use of a token yet. Again, I don't see a way forward that doesn't involve
asking users to log in twice.

I would appreciate any further insights or guidelines about migrating existing
credentials and supporting legacy APIs while we transition.

Thanks,
  Koke

[1] https://github.com/WP-API/authentication/issues/1
[2] https://apps.wordpress.com/mobile/
[3] https://tools.ietf.org/wg/oauth/minutes?item=minutes-104-oauth-00.html

--
Jorge Bernal | jbernal@gmail.com | jorge@automattic.com
Mobile Engineer @ Automattic | http://automattic.com/

http://koke.me/ | http://twitter.com/koke




--
Jorge Bernal | jbernal@gmail.com | jorge@automattic.com
Mobile Engineer @ Automattic | http://automattic.com/

http://koke.me/ | http://twitter.com/koke