[OAUTH-WG] Potential new OAuth client assertion flow
Omer Levi Hevroni <omerlh@gmail.com> Wed, 14 February 2018 20:49 UTC
Return-Path: <omerlh@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 1DE251250B8 for <oauth@ietfa.amsl.com>; Wed, 14 Feb 2018 12:49:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level:
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 EYfghtxKrjak for <oauth@ietfa.amsl.com>; Wed, 14 Feb 2018 12:48:56 -0800 (PST)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (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 7F91A1200FC for <oauth@ietf.org>; Wed, 14 Feb 2018 12:48:56 -0800 (PST)
Received: by mail-oi0-x229.google.com with SMTP id r144so2427138oie.6 for <oauth@ietf.org>; Wed, 14 Feb 2018 12:48:56 -0800 (PST)
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=WPDuf0EKw/QR9Og0/yJbgd8YTDW0704SlnUoRYkEpR0=; b=XlylfFrlGFS25Bx3yU8hieAtA/xavh/MY+CbqPkKfHnwdQKxowH0r61qfnrdWDmToJ 0GdEh7aYyXMbQHkXosCuIWrZWhF+9WyGGHZmpXU8cL9pqXgufptxVBcWuhsy32+lLTJU 9YqL+PHcaYfzt5wo1Z15JpcVyGd3W+4f23+F+uGODsjrcVrsgBo2y33XgWukl2ykWQ4z c7bnlYAMXcnXCdUy2Azso9pRjP3crrRuds5TKJYmNZJjDtllzp8qqpl1bu2oixRwGP5s ioi+KOQ+uJrKecFg3GwFH6ajkYg/KdLX/gHqJoNN7oU+B1aEYh3GKHAkFajd2XZ/kPYH DD3Q==
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=WPDuf0EKw/QR9Og0/yJbgd8YTDW0704SlnUoRYkEpR0=; b=G4ldUSZZQkLk8w9+sGJyKQ/fCJynSCvjMErrA3mkWkaCyRX/A71KZ9JQqbTv86UudY 0SGmZX/E1EBYbDsLgKqgrTF1TEWDfFIhKhnstyKZyLG3hLFm5UE43qMlKeomp0X1n5C1 gyeOreOy0/VcrbLi6lHBe8Y0ahIowitoQLp5swUGBOJ8JR1mGHvtJrw4NcqxuJf6Ymnn ErROHytWPHdGFIaLmjS6HOfHKADpRsaswOl4jzzF8vCDqLJXEnUVSGvMCLD7soT3tNca vEVBAKMrjvvilim4eKGXvgGmS/enWgQu8Z1sA4CCXsxFuL+9z8SADYzHRhplIS2smX5p aXog==
X-Gm-Message-State: APf1xPDC01cH0kPPdtd9FRV3gZIMmZnaHKYiDbZdlXUA31Lo4zgJof5E 1DiKtSQKvepFfPQRicb+ZNMGE3OVcBW84eMMeMNmLQ==
X-Google-Smtp-Source: AH8x225d5bnVNYxGN7GYHLZKYAieKDlrzih1Kb4b2GZtoU9qKIbwFQFd9p7bToV6Q2J5MO/+3IMRsTYQd8e5FP+cvmM=
X-Received: by 10.202.192.137 with SMTP id q131mr287535oif.276.1518641335483; Wed, 14 Feb 2018 12:48:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.89.150 with HTTP; Wed, 14 Feb 2018 12:48:34 -0800 (PST)
From: Omer Levi Hevroni <omerlh@gmail.com>
Date: Wed, 14 Feb 2018 22:48:34 +0200
Message-ID: <CAHuoes4VmfNKetbCum+xMfA=fF4NoYU=9YDoEwC47QDeYRnCcQ@mail.gmail.com>
To: oauth@ietf.org
Content-Type: multipart/alternative; boundary="001a113de04857c4480565323d6b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/D6_AqlF1_FI-mnokAdQMpwU3CDw>
Subject: [OAUTH-WG] Potential new OAuth client assertion flow
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: Wed, 14 Feb 2018 20:49:00 -0000
Hello My name is Omer, and I am working at Soluto. We wanted to find a way to authenticate our mobile application, without any user interaction - as this will affect the user experience. We developed a new authentication flow, similar to JWT client assertion. I've gave a talk about this flow in a few conferences, and the main feedback was that it is interesting enough to consider writing a RFC about it. Currently I'm looking to hear more opinions before starting to write RFC - so any feedback will be appreciated. I'm also looking for someone to help me getting started and reviewing the RFC - if you're interested let me know. To find more about this solution: - This is a blog post describing it: https://blog.solutotlv.com /userless-mobile-authentication/ - This is a link to the slides (recording should be available soon): https://www.slideshare.net/SolutoTLV/authentication-w ithout-authentication-appsec-california Thanks Omer
- [OAUTH-WG] Potential new OAuth client assertion f… Omer Levi Hevroni
- Re: [OAUTH-WG] Potential new OAuth client asserti… Vladimir Dzhuvinov
- Re: [OAUTH-WG] Potential new OAuth client asserti… Omer Levi Hevroni