Closed Bug 8213 Opened 25 years ago Closed 25 years ago

[NEWS]Remember username/password in newsgroup

Categories

(MailNews Core :: Backend, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: sspitzer, Assigned: sspitzer)

References

Details

from news://news.mozilla.org/3761E26C.C450C3DA%40yknet.yk.ca "How about an option in Messenger to remember my news server username and password? It's a pain to have to type it in the first time I get news messages after starting Messenger." I've added this to http://www.mozilla.org/mailnews/jobs.html
Severity: normal → enhancement
OS: Linux → All
Hardware: PC → All
changing severity to enhancement.
Status: NEW → ASSIGNED
accepting bug.
QA Contact: lchiang → scurtis
<updated qa contact name>
I would think single-signon will be able to handle this. I haven't set up newsgroups yet with 5.0 to test this though. cc'ing morse also for his wisdom.
Assignee: sspitzer → morse
Status: ASSIGNED → NEW
Target Milestone: M15 → M9
Single signon does handle this or at least it did at one time. Many changes have occured since I initially put the code into mail/news to do this so it might not be working any more. I haven't checked it lately and don't intend to do so until after necko lands because so many of the single-signon dialogs are currently busted due to lack of necko. After necko lands I will be testing all places where single signon is supposed to kick in and replace the single signon call from any modules from which someone has removed it (e.g., it has been yanked out of site authentication because of the dialog problems). I'll keep this bug report as a reminder that I need to do this clean-up and will close it out once I do.
Severity: enhancement → normal
Summary: [NEWS] RFE: Remember username/password in newsgroup → [NEWS] Remember username/password in newsgroup
Removing the [RFE] designation from the Summary line. This is not an enhancement but rather was always intended as part of the functionality of single-signon. Changing severity from "enhancement" to "normal" for the same reason.
Status: NEW → ASSIGNED
Depends on: 10582
Target Milestone: M9 → M10
Moving this from M9 to M10 because it depends on 10582 which is marked M10.
Depends on: 6144
why is this assigned to morse? also, adding mscott to the cc line. he's revamping / combining the pop & imap password work (and using the signon / wallet stuff too, I think.) when I get to news passwords, I'm going to talk to him. If no one objects, I'm going to re-assign this to me.
morse assigned it to himself (per bug activity log)
I assigned it to myself because I was going to attach single signon wherever it was appropriate (basic site authentication, mailnews, etc.). To that end I have made several changes to single singon this past week-end and even provided mscott with patches to be put into mailnews to use the single signon. But if you want to be responsible for actually putting the patches into mailnews now that I have the single-signon side ready for it, then by all means do so. I don't care who's name is on it as long as the job gets done.
Assignee: morse → sspitzer
Status: ASSIGNED → NEW
Target Milestone: M10 → M11
re-assigning to me. when the time comes, I'll work with mscott to use his common password code, that he's worked with morse to integrate with single sign on. also, setting target milestone to m11.
Status: NEW → ASSIGNED
Triage to M15
QA Contact: scurtis → huang
Change QA Contact to me since it's my feature now.
*** Bug 11047 has been marked as a duplicate of this bug. ***
Blocks: 7530
fixed.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Remember username/password is working on newsgroup "news://poisonivy/xrated" now.... OK for 02-11-08-M14 WinNT commercial build OK for 02-11-11-M14 Linux commercial build OK for 02-11-12-M14 Mac commercial build Marking as verified!!
Status: RESOLVED → VERIFIED
Summary: [NEWS] Remember username/password in newsgroup → [NEWS]Remember username/password in newsgroup
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.