Return-Path: 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 D27BA3A67D4 for ; Tue, 13 Jul 2010 16:34:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.467 X-Spam-Level: X-Spam-Status: No, score=-2.467 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 j3cFtxxKhj-q for ; Tue, 13 Jul 2010 16:34:17 -0700 (PDT) Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id 03BD33A6881 for ; Tue, 13 Jul 2010 16:34:16 -0700 (PDT) Received: (qmail 28376 invoked from network); 13 Jul 2010 23:34:25 -0000 Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 13 Jul 2010 23:34:25 -0000 Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Tue, 13 Jul 2010 16:34:22 -0700 From: Eran Hammer-Lahav To: Zachary Zeltsan , Brian Eaton , "Faynberg, Igor (Igor)" Date: Tue, 13 Jul 2010 16:34:20 -0700 Thread-Topic: [OAUTH-WG] "shared symmetric secret" Thread-Index: AcsizAn9v2oizrpATQOFeGWmraNc5AABr+MQAARIR20= Message-ID: In-Reply-To: <5710F82C0E73B04FA559560098BF95B124F9688DC4@USNAVSXCHMBSA3.ndc.alcatel-lucent.com> Accept-Language: en-US Content-Language: en X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_C862460C37210eranhueniversecom_" MIME-Version: 1.0 Cc: OAuth WG Subject: Re: [OAUTH-WG] "shared symmetric secret" X-BeenThere: oauth@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: OAUTH WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jul 2010 23:34:22 -0000 --_000_C862460C37210eranhueniversecom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm only using 2828 definition of capability, not password. EHL On 7/13/10 3:20 PM, "Zachary Zeltsan" = wrote: According to the RFC 2828 an access token is rather a capability than a pas= sword. The passwords are usually associated with the matching identifiers, = but an access token of OAuth 2.0 is used as a single credential that allows= access to a protected resource. >From RFC 2828: $ password (C) A password is usually matched with a user identifier that is explicitly presented in the authentication process, but in some cases the identity may be implicit. Zachary -----Original Message----- From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of B= rian Eaton Sent: Tuesday, July 13, 2010 4:43 PM To: Faynberg, Igor (Igor) Cc: OAuth WG Subject: Re: [OAUTH-WG] "shared symmetric secret" On Tue, Jul 13, 2010 at 1:40 PM, Igor Faynberg wrote: > In this case, the term "capability" MUST be defined up front. The word > "capability" seems to carry a much broader meaning than password... It has a standard definition we can reference. From http://www.ietf.org/rfc/rfc2828.txt $ capability (I) A token, usually an unforgeable data value (sometimes called a "ticket") that gives the bearer or holder the right to access a system resource. Possession of the token is accepted by a system as proof that the holder has been authorized to access the resource named or indicated by the token. (See: access control list, credential, digital certificate.) _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth --_000_C862460C37210eranhueniversecom_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: [OAUTH-WG] "shared symmetric secret" I’m only using 2828 definition of capability, not password.

EHL


On 7/13/10 3:20 PM, "Zachary Zeltsan" <zachary.zeltsan@alcatel-lucent.com> wrote:
According to the RFC 2828 an access token i= s rather a capability than a password. The passwords are usually associated= with the matching identifiers, but an access token of OAuth 2.0 is used as= a single credential that allows access to a protected resource.

>From RFC 2828:
$ password
     
      (C) A password is usually matched with = a user identifier that is
      explicitly presented in the authenticat= ion process, but in some
      cases the identity may be implicit.

Zachary
-----Original Message-----
From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On B= ehalf Of Brian Eaton
Sent: Tuesday, July 13, 2010 4:43 PM
To: Faynberg, Igor (Igor)
Cc: OAuth WG
Subject: Re: [OAUTH-WG] "shared symmetric secret"

On Tue, Jul 13, 2010 at 1:40 PM, Igor Faynberg
<igor.faynberg@alcatel-luce= nt.com> wrote:
> In this case, the term "capability" MUST be defined up front= . The word
> "capability" seems to carry a much broader meaning than pass= word...

It has a standard definition we can reference.  From
http://www.ietf.org/rfc/rfc= 2828.txt

   $ capability
      (I) A token, usually an unforgeable dat= a value (sometimes called a
      "ticket") that gives the bear= er or holder the right to access a
      system resource. Possession of the toke= n is accepted by a system
      as proof that the holder has been autho= rized to access the
      resource named or indicated by the toke= n. (See: access control
      list, credential, digital certificate.)=

     
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.or= g/mailman/listinfo/oauth
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.or= g/mailman/listinfo/oauth

--_000_C862460C37210eranhueniversecom_--