Last Comment Bug 68409 - W3C CUAP: Provide a mechanism to allow authentication information to expire
: W3C CUAP: Provide a mechanism to allow authentication information to expire
Status: NEW
[necko-would-take]
:
Product: Core
Classification: Components
Component: Networking: HTTP (show other bugs)
: Trunk
: x86 All
: -- enhancement with 6 votes (vote)
: Future
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
http://www.w3.org/TR/2001/NOTE-cuap-2...
Depends on: 260839 55181
Blocks: 68427
  Show dependency treegraph
 
Reported: 2001-02-10 01:28 PST by Gervase Markham [:gerv]
Modified: 2016-01-19 11:00 PST (History)
7 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Gervase Markham [:gerv] 2001-02-10 01:28:58 PST
[ This bug is one of the recommendations in the W3C's "Common User Agent 
Problems" document, URL above. One bug has been filed on each recommendation, 
for deciding whether we do it and, if not, whether we should. ]

1.8 Provide a mechanism to allow authentication information to expire.

     Many browsers allow configuration to save HTTP authentication
     [RFC2616, RFC2617] information ("remember my password"). They should
     also allow users to "flush" that authentication information on
     request. For instance, the user may wish to leave the user agent
     running but tell it to forget the password to access the user's bank
     account.

     Wrong: Most user agents consider that authentication information
     (e.g., password) provided by a user for a server/realm pair during a
     session is immutable for the duration of the session.
Comment 1 Matthew Paul Thomas 2001-02-10 03:39:39 PST


*** This bug has been marked as a duplicate of 55181 ***
Comment 2 Gervase Markham [:gerv] 2001-02-10 08:00:39 PST
The bug, which is about compliance with the guidelines, is blocked by bug 55181.
Marking as such, and reopening. We should only close this bug when we comply :-)

Gerv
Comment 3 Mitchell Stoltz (not reading bugmail) 2001-02-12 13:42:56 PST
Reassigning to Gagan.
Comment 4 Gervase Markham [:gerv] 2001-03-01 10:44:18 PST
mstolz: You said "Assigning to gagan" and assigned to neeti@netscape.com. Isn't 
gagan gagan@netscape.com?

Gerv
Comment 5 benc 2001-05-23 12:33:17 PDT
mass move, v2.
qa to me.
Comment 6 Doug Turner (:dougt) 2002-10-01 12:55:07 PDT
moving neeti's futured bugs for triaging.
Comment 7 benc 2002-10-04 08:59:06 PDT
-> defaults
Comment 8 Darin Fisher 2002-10-04 09:14:42 PDT
hmm... there's other bugs already on file having to do with providing an
explicit logout mechanism... this RFE should probably be included/considered
with the work to solve that bug.
Comment 9 Gervase Markham [:gerv] 2013-07-30 03:30:49 PDT
https://addons.mozilla.org/en-US/firefox/addon/http-logout/ does this.

Gerv

Note You need to log in before you can comment on or make changes to this bug.