Re: [OAUTH-WG] SAML profile comments/questions from the SAML people

Brian Campbell <bcampbell@pingidentity.com> Thu, 12 August 2010 20:07 UTC

Return-Path: <bcampbell@pingidentity.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EA493A6840 for <oauth@core3.amsl.com>; Thu, 12 Aug 2010 13:07:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.8
X-Spam-Level:
X-Spam-Status: No, score=-5.8 tagged_above=-999 required=5 tests=[AWL=0.177, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vqiaF5zR1RZ8 for <oauth@core3.amsl.com>; Thu, 12 Aug 2010 13:07:53 -0700 (PDT)
Received: from na3sys009aog101.obsmtp.com (na3sys009aog101.obsmtp.com [74.125.149.67]) by core3.amsl.com (Postfix) with SMTP id CB6703A67AE for <oauth@ietf.org>; Thu, 12 Aug 2010 13:07:52 -0700 (PDT)
Received: from source ([209.85.215.175]) by na3sys009aob101.postini.com ([74.125.148.12]) with SMTP ID DSNKTGRUvXOp8Wam1usv2aITDkQDqBjPUJwL@postini.com; Thu, 12 Aug 2010 13:08:30 PDT
Received: by eyx24 with SMTP id 24so1247512eyx.34 for <oauth@ietf.org>; Thu, 12 Aug 2010 13:08:29 -0700 (PDT)
Received: by 10.216.62.206 with SMTP id y56mr396327wec.59.1281643709173; Thu, 12 Aug 2010 13:08:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.60.136 with HTTP; Thu, 12 Aug 2010 13:07:59 -0700 (PDT)
In-Reply-To: <C8897B1F.B75B%cmortimore@salesforce.com>
References: <AANLkTim7qdDm45N7D-7Zoo9Ew3g1ibQg7CWoUzX+ds61@mail.gmail.com> <C8897B1F.B75B%cmortimore@salesforce.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Thu, 12 Aug 2010 14:07:59 -0600
Message-ID: <AANLkTikTGa+Pss_oT8FouqaqH7pAY_EiRukTsSuPFaVw@mail.gmail.com>
To: Chuck Mortimore <cmortimore@salesforce.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: oauth <oauth@ietf.org>
Subject: Re: [OAUTH-WG] SAML profile comments/questions from the SAML people
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 12 Aug 2010 20:07:54 -0000

On Thu, Aug 12, 2010 at 11:19 AM, Chuck Mortimore
<cmortimore@salesforce.com> wrote:
> I think it would be reasonable to loosen the language to reflect that the
> subject is who access will be granted to.   It may or may not be the
> resource owner, I agree.

Any thoughts on what that would look like in the spec?    Something
like "The assertion MUST contain a <Subject> element.  The <Subject>
MAY identify the resource owner for whom the access token is being
requested."?   Or just drop the language about resource owner all
together?  Or something else?

What about the two bullets on AuthnStatement?

   o  If the assertion issuer authenticated the subject, the assertion
      SHOULD contain a single <AuthnStatement> representing that
      authentication event.

   o  If the assertion was issued with the intention that the client act
      autonomously on behalf of the subject, an <AuthnStatement> SHOULD
      NOT be included.

They kind of, but not completely, imply/assume some explicit
relationship between the subject and resource owner.