[OAUTH-WG] Fwd: [OAuth2.0][SAML2.0] 2.2. Using SAML Assertions for Client Authentication Problem ?

Brian Campbell <bcampbell@pingidentity.com> Wed, 01 February 2012 16:07 UTC

Return-Path: <bcampbell@pingidentity.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 E473B11E80BA for <oauth@ietfa.amsl.com>; Wed, 1 Feb 2012 08:07:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.56
X-Spam-Level:
X-Spam-Status: No, score=-5.56 tagged_above=-999 required=5 tests=[AWL=0.417, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iodXKjkHFIxp for <oauth@ietfa.amsl.com>; Wed, 1 Feb 2012 08:07:52 -0800 (PST)
Received: from na3sys009aog109.obsmtp.com (na3sys009aog109.obsmtp.com [74.125.149.201]) by ietfa.amsl.com (Postfix) with ESMTP id EE94411E80A3 for <oauth@ietf.org>; Wed, 1 Feb 2012 08:07:51 -0800 (PST)
Received: from mail-vx0-f177.google.com ([209.85.220.177]) (using TLSv1) by na3sys009aob109.postini.com ([74.125.148.12]) with SMTP ID DSNKTyljV47xwAQIZWJv++hMpxflZmxCp0HH@postini.com; Wed, 01 Feb 2012 08:07:52 PST
Received: by mail-vx0-f177.google.com with SMTP id f1so1316544vcb.8 for <oauth@ietf.org>; Wed, 01 Feb 2012 08:07:51 -0800 (PST)
Received: by 10.220.148.132 with SMTP id p4mr15256887vcv.31.1328112470832; Wed, 01 Feb 2012 08:07:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.37.42 with HTTP; Wed, 1 Feb 2012 08:07:18 -0800 (PST)
In-Reply-To: <CAAX2Qa0iFZtuX2sLUh5WBwZCYX81RuPjT=Cr=LHmL0gL1-cFAw@mail.gmail.com>
References: <CAHA4TYvE0Ng1E+MtWqVifgZrsoj6RKgKmOZEG9RYeSwnz8Mjew@mail.gmail.com> <CAAX2Qa3iDxhr3W_vOtYt=OpwNs2wNy6yf+HfgCGVxDPdGaM5iA@mail.gmail.com> <CAAX2Qa0iFZtuX2sLUh5WBwZCYX81RuPjT=Cr=LHmL0gL1-cFAw@mail.gmail.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Wed, 01 Feb 2012 09:07:18 -0700
Message-ID: <CA+k3eCT+GNFXk+YS59Z23bz0vceMj7C=QWcTgw1ZkiK00Z-3UQ@mail.gmail.com>
To: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="f46d043c09220bb66b04b7e9481d"
Subject: [OAUTH-WG] Fwd: [OAuth2.0][SAML2.0] 2.2. Using SAML Assertions for Client Authentication Problem ?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 01 Feb 2012 16:07:53 -0000

I wanted to get the below question and answer to the right place.

---------- Forwarded message ----------
From: Brian Campbell <brian.d.campbell@gmail.com>
Date: Wed, Feb 1, 2012 at 9:01 AM
Subject: Re: [OAuth2.0][SAML2.0] 2.2. Using SAML Assertions for Client
Authentication Problem ?
To: Shiu Fun Poon <shiufunpoon@gmail.com>
Cc: cmortimore@salesforce.com


Hi Shiu,

Section 2.2 is about client authentication and the parameter names are
correct for that context (the names are defined in
http://tools.ietf.org/html/draft-ietf-oauth-assertions and this profile
defines the values for use with SAML).

The example in Section 4 that uses assertion and grant_type is about
authorization and not client authentication. And it is consistent with
section 2.1

Thanks,
B

On Tue, Jan 31, 2012 at 10:29 PM, Shiu Fun Poon <shiufunpoon@gmail.com>wrote:

> Hi..
> Reading the latest spec.. are there typos in the following section ?
>
> 2.2.  Using SAML Assertions for Client Authentication
>
>
> he value of "client_assertion_type" parameter MUST  ??  Should this be grant_type
> The value of the "client_assertion" parameter   ?? Is this assertion (which is what is shown in the example).
>
>
>
>
> Thanks.
>
>