IETF Logo Mail Archive

[OAUTH-WG] JWT Token on-behalf of Use case

"Vivek Biswas -T (vibiswas - XORIANT CORPORATION at Cisco)" <vibiswas@cisco.com> Thu, 25 June 2015 21:19 UTC

Return-Path: <vibiswas@cisco.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 CF0791B2AAA for <oauth@ietfa.amsl.com>; Thu, 25 Jun 2015 14:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.611
X-Spam-Level:
X-Spam-Status: No, score=-12.611 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 1TJzv5SV97SW for <oauth@ietfa.amsl.com>; Thu, 25 Jun 2015 14:19:44 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E40F1B2AA8 for <OAuth@ietf.org>; Thu, 25 Jun 2015 14:19:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12866; q=dns/txt; s=iport; t=1435267184; x=1436476784; h=from:to:subject:date:message-id:mime-version; bh=2fsZPz12B3J3YK2YZQ6EWIQVMB6ZHVh5vBXV1RTiXoY=; b=NaucmckjmzbD8oGQaC2t0+lxRGOijMlAGItBKXG0HMXY091JOtaOBpba GFUefttr9aDXCnhBjYumqrcQXbgHqxYbKQQF2ylBZ6zw15symZDzPmH+r 4FwlTT6SYCC6rCRZGNoyI4b9B/4FRPbkfw+1jZIk++7ul+RH8YSl/HpAh Q=;
X-Files: image003.jpg : 5264
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AGCABvb4xV/5NdJa1ZA4JFTFRfAQW8KDyCHXeEfQKBQDwQAQEBAQEBAYEKhCQBBAUgCAFZBAEPFgEBAQIIHgUQAQMEBwwmAQQSAQYCBoghDadtpjkBAQEBAQEBAQEBAQEBAQEBAQEBAQEXBIZViUYWCyiDBoEUBZQGAQeDbAFjiHaDVZJoERVjgxdvAQEBgUOBAgEBAQ
X-IronPort-AV: E=Sophos;i="5.13,679,1427760000"; d="jpg'145?scan'145,208,217,145";a="10383869"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-3.cisco.com with ESMTP; 25 Jun 2015 21:19:43 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t5PLJhBt015166 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <OAuth@ietf.org>; Thu, 25 Jun 2015 21:19:43 GMT
Received: from xmb-aln-x09.cisco.com ([169.254.4.112]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0195.001; Thu, 25 Jun 2015 16:19:43 -0500
From: "Vivek Biswas -T (vibiswas - XORIANT CORPORATION at Cisco)" <vibiswas@cisco.com>
To: "OAuth@ietf.org" <OAuth@ietf.org>
Thread-Topic: JWT Token on-behalf of Use case
Thread-Index: AdCvjKZzog4lHzdSReisaGHaz/hQ6g==
Date: Thu, 25 Jun 2015 21:19:42 +0000
Message-ID: <6B22D19DBF96664DBF49BC7B326402B42739A904@xmb-aln-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.24.242.89]
Content-Type: multipart/related; boundary="_004_6B22D19DBF96664DBF49BC7B326402B42739A904xmbalnx09ciscoc_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/Wbr_swXhKqbXD2PlgmX3T4W9kDk>
Subject: [OAUTH-WG] JWT Token on-behalf of Use case
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: <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, 25 Jun 2015 21:20:27 -0000

Hi All,

  I am looking to solve a use-case similar to WS-Security On-Behalf-Of<http://docs.oasis-open.org/ws-sx/ws-trust/v1.4/errata01/os/ws-trust-1.4-errata01-os-complete.html#_Toc325658980> with OAuth JWT Token.

  Is there a standard claim which we can define within the OAuth JWT which denote the On-behalf-of User.

For e.g., a Customer Representative trying to create token on behalf of a customer and trying to execute services specific for that specific customer.
Regards,
Vivek Biswas,
[CISSP]

Cisco Systems, Inc<http://www.cisco.com/>
Bldg. J, San Jose, USA,
Phone: +1 408 527 9176

v2.23.0 | Report a Bug | By Email