You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "William A. Rowe, Jr." <wr...@rowe-clan.net> on 2005/09/29 23:10:09 UTC

[Fwd: HTTP authentication]

I expect some on this list would be interested in the discussion
list below.


-------- Original Message --------
Subject: HTTP authentication
Date: Thu, 29 Sep 2005 13:07:54 -0700
From: Lisa Dusseault <li...@osafoundation.org>
To: HTTP working group <ie...@w3.org>,	CalDAV DevList 
<ie...@osafoundation.org>,	WebDav WG <w3...@w3.org>


Talking with various potential CalDAV deployers lately, there's a
perceived need for better HTTP authentication mechanisms: ones which
can deal with federated identity and single sign-on.  I've also heard
people respond "what's the problem? Put an authentication proxy in the
proxy path" or suggest HTTP-SASL or a number of other possible
solutions to possible problems.

So, we probably need first to discuss whether there is a problem, and
if so, what to do about it.  There's been a suggestion to hold a BOF in
Vancouver (if it's not too late to plan one) to see who the interested
parties are and start defining (or defining away) the problem.  Another
idea is to hold a workshop at some point after we've identified the
interested parties.

Anyway, I've started a separate discussion list for this topic-- I
didn't want to spam the general HTTP list or make people who weren't
interested in general HTTP issues (but only in authentication for
CalDAV/WebDAV) join that list.  Please join and chime in any time about
what you perceive the problem or lack of problem to be or leap straight
to what ought to be done.

http://lists.osafoundation.org/cgi-bin/mailman/listinfo/ietf-http-auth

Lisa