Re: [OAUTH-WG] Definition of additional client profiles

John Bradley <ve7jtb@ve7jtb.com> Thu, 02 October 2014 21:48 UTC

Return-Path: <ve7jtb@ve7jtb.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 BBE741ACE2A for <oauth@ietfa.amsl.com>; Thu, 2 Oct 2014 14:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 k0FGfN2XuEQe for <oauth@ietfa.amsl.com>; Thu, 2 Oct 2014 14:48:42 -0700 (PDT)
Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51A651ACE20 for <oauth@ietf.org>; Thu, 2 Oct 2014 14:48:42 -0700 (PDT)
Received: by mail-qa0-f54.google.com with SMTP id i13so471qae.41 for <oauth@ietf.org>; Thu, 02 Oct 2014 14:48:41 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=3YA1a9w1A7JbGPOsvLkt6obAWuuty5nIY5aH5K6+lcg=; b=dpHpRA8HQC9BgVnmrv65ltbOTJwREkVu96CKarrtAGDvfPWTnCTnlsPokkMcKoqT17 eBZwgX/+IbOETDkWwkD4EDHnspbedqqoqGopwi5n6rSbCl723ligJIUw6fO5/VO8jbsf y84MNoixWbcHT5Gyb6UKI8TQRSZHTS/Qxj4Uek/HJ5ADvkSenI/Ezhjft5VMpVAYH7Yl BaypafAyxdWBG0YQP5frGukAvmmBU8dQHRhGmgcsQSp86LLpE3AMBo/DGGAXH9hZujZU 7vpzrFOrN1cVSjwmQ1x4tHUNAxPSzH83ZwtpN2YMDZ7q3ShC6F1vmvoInWkz5/gOHnks XoCQ==
X-Gm-Message-State: ALoCoQlFQEXDpBS9kjelxL7o82efPtx7r5XIG02nlzpUq5M0tk4cZFUJtESkxOMqpJNee6J6fZQo
X-Received: by 10.140.85.227 with SMTP id n90mr2002511qgd.89.1412286521277; Thu, 02 Oct 2014 14:48:41 -0700 (PDT)
Received: from [192.168.1.216] (186-106-131-109.baf.movistar.cl. [186.106.131.109]) by mx.google.com with ESMTPSA id g5sm4224794qaz.39.2014.10.02.14.48.39 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Oct 2014 14:48:40 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_7CF43E30-A42E-4F15-A8B1-CD8E2BD7882C"; protocol="application/pkcs7-signature"; micalg="sha1"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <2e05cf8c68364a3b94aca4b370af344d@DM2PR04MB735.namprd04.prod.outlook.com>
Date: Thu, 02 Oct 2014 18:48:54 -0300
Message-Id: <948F628D-93B9-49B5-B725-603B09B90882@ve7jtb.com>
References: <2e05cf8c68364a3b94aca4b370af344d@DM2PR04MB735.namprd04.prod.outlook.com>
To: Adam Lewis <Adam.Lewis@motorolasolutions.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/pji6VGOU2tpqiBS9OW4rDUXR6Po
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Definition of additional client profiles
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: Thu, 02 Oct 2014 21:48:48 -0000

Additional authentication types have been defined have been defined for confidential clients, such as SAML and JWT assertion.  http://tools.ietf.org/html/draft-ietf-oauth-assertions

There will likely be more of that, but I don't think there are likely to be other client types beyond the two. 

John B.

On Oct 2, 2014, at 5:19 PM, Lewis Adam-CAL022 <Adam.Lewis@motorolasolutions.com> wrote:

> Hi,
>  
> 6749 defines three client profiles which are mapped to either confidential or public client types.
>  
> Have any new client profiles since been defined?  And is there a process or place to put those additional profiles?
>  
> For example I’m thinking about additional confidential client types, maybe a legacy WS-* WSC accessing a WS-* WSP, and that WSP is acting as a confidential client to a RESTful RS.
>  
> Just curious if further definitions are being collected anywhere.  I’m not sure if it really matters, maybe confidential is confidential, regardless of if it’s a web server or a WS-* WSP, but since the spec went as far as to define the client profiles then maybe there is a place to define more.
>  
>  
>  
> Tx!
> adam
>  
>  
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth