Re: [http-auth] REST-GSS I-D posted

"KIHARA, Boku" <bkihara.l@gmail.com> Wed, 08 June 2011 08:59 UTC

Return-Path: <bkihara.l@gmail.com>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3FF111E8128 for <http-auth@ietfa.amsl.com>; Wed, 8 Jun 2011 01:59:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level:
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_17=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WQ7fjuDXHa0Q for <http-auth@ietfa.amsl.com>; Wed, 8 Jun 2011 01:59:59 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4767A11E810A for <http-auth@ietf.org>; Wed, 8 Jun 2011 01:59:59 -0700 (PDT)
Received: by pvh18 with SMTP id 18so162503pvh.31 for <http-auth@ietf.org>; Wed, 08 Jun 2011 01:59:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=zRtZq+ufWXW6DLpv0wP3qq2NppW2/7R5kR9fXiDFrjg=; b=XyNKT7NvL1GCJRZZ9Rg4UMQAY5w3JYuuLTvJpGF+rC73RfQP0ZR7NAHN8Mv8sCkMiw zPKjMjxWVF/VJ9qenUSLQN/Mx9xaRcQK+b+uMANVluJ22mVz5MRSJq5qNOdr6DNerv6M 8PnuLOVK4mZmvWGxit3N/fcv9LiGBq4ydcrXA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=nNA6dQyEHKnPt0qlbCkKOPZdHSyZyUmk9En2f73PPlV3cjgmLd7T+09E0TF3JPYyny DIXrDUzovkZDGFBCB6/o04CdOZm2VM6/gtm4v/2xcJmo5av/yfZU3e53KwJ1QDzvjo/V vObQwdnnl8xiylQsPZWT7BcevmQeODHAFTesQ=
MIME-Version: 1.0
Received: by 10.143.97.42 with SMTP id z42mr202546wfl.359.1307523597703; Wed, 08 Jun 2011 01:59:57 -0700 (PDT)
Received: by 10.142.164.3 with HTTP; Wed, 8 Jun 2011 01:59:57 -0700 (PDT)
In-Reply-To: <BANLkTimAw-HG9xVzumzbBKhW+H7WGB8+DA@mail.gmail.com>
References: <BANLkTimAw-HG9xVzumzbBKhW+H7WGB8+DA@mail.gmail.com>
Date: Wed, 08 Jun 2011 17:59:57 +0900
Message-ID: <BANLkTikKts6YfAXqcWnD+689wv5iW3M5Cw@mail.gmail.com>
From: "KIHARA, Boku" <bkihara.l@gmail.com>
To: Nico Williams <nico@cryptonector.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: http-auth@ietf.org
Subject: Re: [http-auth] REST-GSS I-D posted
X-BeenThere: http-auth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: HTTP authentication methods <http-auth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-auth>, <mailto:http-auth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-auth>
List-Post: <mailto:http-auth@ietf.org>
List-Help: <mailto:http-auth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-auth>, <mailto:http-auth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 09:00:00 -0000

Dear Nico,

I'm reading the REST-GSS I-D and have several comments on it.

> 2.9.  Server Indication of Authentication Requirement
>
>    When the server wishes to indicate that the client must authenticate
>    in order to access a given resource, then the server MUST respond to
>    the client's HTTP request with either a redirection to a web page
>    with a 303 redirect to a login page (this in the case of browser
>    applications) or a TBD 4xx error indicating that access requires
>    REST-GSS login and, optionally directing the client to the REST-GSS
>    login URI by listing that URI in a response header field named 'REST-
>    GSS-Authenticate'.
>

I'm not sure whether the 'REST-GSS-Authenticate' field is allowed for
only 4xx responses or both 303 and 4xx responses.

> 3.1. Server Decides When to Authenticate
>       C->S: HTTP/1.1 GET /some/resource
>             Host: A.example
>
>       S->C: HTTP/1.1 303 http://A.example/login.html&<encoded-URI>
>
>               Authentication required indication browser apps

Is the URI 'http://A.example/login.html&<encoded-URI>' intended for
the 'Location' field?

What is the clinging '<encoded-URI>'? If it is the REST-GSS login
URI, what is the purpose of this URI here? I think browsers cannot
(or should not) detect the REST-GSS login URI because it is merely a
part of the redirection URI, and servers do not need the '<encoded-URI>'
because they already know the REST-GSS login URI.

>       C->S: HTTP/1.1 GET /some/resource
>             Host: A.example
>
>       S->C: HTTP/1.1 4xx
>             REST-GSS-URI: http://A.example/rest-gss-login
>
>           Authentication required indication for non-browser apps

In this example, the 4xx response has the filed have a field named
'REST-GSS-URI', which is different from 'REST-GSS-Authenticate'
mentioned in 2.9. So which is correct or am I referring different
things?


Sorry for my poor English and small amount of comments, but I hope these help.

Regards,

--
KIHARA, Boku


2011/6/7 Nico Williams <nico@cryptonector.com>:
> http://www.ietf.org/id/draft-williams-rest-gss-00.txt
>
> This is to go with the slides and paper presented almost two weeks ago
> at the W3C workshop on identity in the browser:
>
> http://www.w3.org/2011/identity-ws/agenda.html
>
> I would like to add some co-authors.  Anyone interested?
>
> Cheers,
>
> Nico
> --
> _______________________________________________
> http-auth mailing list
> http-auth@ietf.org
> https://www.ietf.org/mailman/listinfo/http-auth
>