[OAUTH-WG] Confirmation (was draft-ietf-oauth-saml2-bearer-17)

Brian Campbell <bcampbell@pingidentity.com> Mon, 04 November 2013 20:00 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 8CBB621E8269 for <oauth@ietfa.amsl.com>; Mon, 4 Nov 2013 12:00:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.928
X-Spam-Level:
X-Spam-Status: No, score=-5.928 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 LveuNdkKz-m1 for <oauth@ietfa.amsl.com>; Mon, 4 Nov 2013 12:00:19 -0800 (PST)
Received: from na3sys009aog105.obsmtp.com (na3sys009aog105.obsmtp.com [74.125.149.75]) by ietfa.amsl.com (Postfix) with ESMTP id 059B121E80DE for <oauth@ietf.org>; Mon, 4 Nov 2013 11:59:58 -0800 (PST)
Received: from mail-ie0-f172.google.com ([209.85.223.172]) (using TLSv1) by na3sys009aob105.postini.com ([74.125.148.12]) with SMTP ID DSNKUnf8u+RJnbwHtmiwbzmRgT+JB56gPY7b@postini.com; Mon, 04 Nov 2013 11:59:59 PST
Received: by mail-ie0-f172.google.com with SMTP id tp5so13508850ieb.17 for <oauth@ietf.org>; Mon, 04 Nov 2013 11:59:47 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc :content-type; bh=32u5OR4lboce9ITUGmxGeWT6oTOfp6d/nw9qTXhvXfQ=; b=MkCDr4lEAQM+2PD7Xz5of5CGwAzOFyvWTzJS/KBzsU0F/Mub5SBaKbYeJlgl5v7Qhc ghngz2/g+1YKjJG7ffVOdjmX9tuROMZjHd3MK1L3aCilZ3qHVtNFWvtnD+W29ED/P1/O BMkrs3kjwBYRjGRUJji03GOHI+sb3sDsdW8fT9KRmS1UHKdsyj8HT5sbtrtYyGfyKcEq DkO/UJeiUbF9087YZAMb5McICAWQPVbqJIbw2+Z6g1M61yK6WUpCkw40VupKRdzEuB2e XGhFnKElRaWLurhTl07KigZldOtuRcG+wNHapA4ukQdijceD06hGNEm2JIqvfGlWxvym 577w==
X-Gm-Message-State: ALoCoQmkbCnIGt8E3mHWcBPO4/4bguhJIAokOQsYpKshsySHdl6NevuzRUWE5NBNLf2ypoktgGOfFQfxf9VQ0WU5XNQHj3ty4stlvMCb90lWSv0miat3w4ZzbsZi9dlpjlyU7FNcl5fKUcmusmwUYMoJQcESuad8qA==
X-Received: by 10.50.56.44 with SMTP id x12mr13267218igp.41.1383595187911; Mon, 04 Nov 2013 11:59:47 -0800 (PST)
X-Received: by 10.50.56.44 with SMTP id x12mr13267213igp.41.1383595187845; Mon, 04 Nov 2013 11:59:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.245.233 with HTTP; Mon, 4 Nov 2013 11:59:17 -0800 (PST)
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Mon, 04 Nov 2013 11:59:17 -0800
Message-ID: <CA+k3eCRb9rXKbhg_ngdfzmutJOUXYNQ+xkfDzZqvY8A7eHVpAA@mail.gmail.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "oauth@ietf.org WG" <oauth@ietf.org>
Subject: [OAUTH-WG] Confirmation (was draft-ietf-oauth-saml2-bearer-17)
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: Mon, 04 Nov 2013 20:00:25 -0000

On Sat, Nov 2, 2013 at 2:07 AM, Hannes Tschofenig
<hannes.tschofenig@gmx.net> wrote:
> Item #5: You write:
>
> "
> The <Subject> element MUST contain at least one
>         <SubjectConfirmation> element that allows the authorization
>         server to confirm it as a Bearer Assertion.
> "
>
> What do you mean that the AS confirms that it is a bearer assertion?

Confirmation is a term from SAML which is honestly not well understood
by many people (myself included) but I'm trying to be consistent with
that in how I use it here. But it's not necessary and #5 is just
stating how the <SubjectConfirmation> element needs to look. Perhaps
rewording it to just not use the confirm language would be better?

> I think
> what you rather want to say is that the AS indicates that it is a bearer
> assertion.

No, it's just language around what needs to be validated in the
<SubjectConfirmation> element of the assertion because it is a bearer
assertion.