IETF Logo Mail Archive

[OAUTH-WG] JWT binding for OAuth 2.0

Prabath Siriwardena <prabath@wso2.com> Tue, 14 April 2015 21:25 UTC

Return-Path: <prabath@wso2.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7F6F1A1AC6 for <oauth@ietfa.amsl.com>; Tue, 14 Apr 2015 14:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.022
X-Spam-Level:
X-Spam-Status: No, score=0.022 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 c431oVZoHkWG for <oauth@ietfa.amsl.com>; Tue, 14 Apr 2015 14:25:51 -0700 (PDT)
Received: from mail-vn0-x235.google.com (mail-vn0-x235.google.com [IPv6:2607:f8b0:400c:c0f::235]) (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 C1E841A3B9C for <oauth@ietf.org>; Tue, 14 Apr 2015 14:21:17 -0700 (PDT)
Received: by vnbg62 with SMTP id g62so8377729vnb.7 for <oauth@ietf.org>; Tue, 14 Apr 2015 14:21:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wso2.com; s=google; h=mime-version:date:message-id:subject:from:to:content-type; bh=yfIqb9dJInPY8IdFywBqusEnjDRSAl/Qo3tbiJPZv60=; b=h92Vk7q23aFwjSZRtDF2tN9+tjvc0h02rHLy3tA+LuO23sCCZtag71E8IM2WxAn9fp mTnBzOb37XI6scSYDNy3tlUh2VUqCiCaw48VBeOeXEP4xtTDGqqyfXmtAASEINKkmjzL f9D1ijDeSYoWERLKQBU38ty3yuhsGssBG5cFM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=yfIqb9dJInPY8IdFywBqusEnjDRSAl/Qo3tbiJPZv60=; b=H81TeVa+tDPd0K0iZWBauMtmsciQLv0HqFZuOxcmwvYmLUDMDg0eOyXKo+RrwuNNAs Xt/9oSPvL2/zOpPN2WmtXsU+SFn8G7mYrvA8zbCqlwXxz8yW1S6CLITcVR24RUKbA9uY 9csQ2zfdQN4NTaZqdtvLRiiZBFkb6sRO1OBQF2ZotcdGk1Pa1nZGoB2mgsFZh8j+IKfo zwPycdGAtPslVceuKpuhWo9gAlXiiv2OYM4K5fzk7UCgc2ViMmTmfKACaXRW0m0z1tBM KaKNt+aDMXVIQ1rkHrLptyMbW3EFf6Uky7+4p6J8NMKwmymooE6KvcB928a7kjgcXw1+ ALEg==
X-Gm-Message-State: ALoCoQkJJxiCa8IzwvK8AKddESlTc1rwosMBuomGX5AVneHVyQwxgz4FJk1XbtxOmhrVFb8/A/yF
MIME-Version: 1.0
X-Received: by 10.182.22.167 with SMTP id e7mr17738238obf.31.1429046476908; Tue, 14 Apr 2015 14:21:16 -0700 (PDT)
Received: by 10.202.72.198 with HTTP; Tue, 14 Apr 2015 14:21:16 -0700 (PDT)
Date: Tue, 14 Apr 2015 14:21:16 -0700
Message-ID: <CAJV9qO-PsiNOdfBAf9k0VJ7+eGkE_g_gbygdCbGMv2UT56Ld=g@mail.gmail.com>
From: Prabath Siriwardena <prabath@wso2.com>
To: "oauth@ietf.org WG" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c2e0ba9fd38d0513b5cf87"
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/o06lfbzBshxdAAGIlRrAcTi_-YE>
Subject: [OAUTH-WG] JWT binding for OAuth 2.0
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 14 Apr 2015 21:25:54 -0000

At the moment we only HTTP binding to transport the access token (please
correct me if not)..

This creates a dependency on the transport.

How about creating a JWT binding for OAuth 2.0..? We can transport the
access token as an encrypted JWT header parameter..?


Thanks & Regards,
Prabath

Twitter : @prabath
LinkedIn : http://www.linkedin.com/in/prabathsiriwardena

Mobile : +1 650 625 7950

http://blog.facilelogin.com
http://blog.api-security.org

v2.23.0 | Report a Bug | By Email