Closed
Bug 34507
Opened 25 years ago
Closed 20 years ago
Asked for authentication twice for password protected news.
Categories
(MailNews Core :: Backend, defect, P3)
MailNews Core
Backend
Tracking
(Not tracked)
People
(Reporter: laurel, Assigned: sspitzer)
References
Details
(Whiteboard: [nsbeta3-][nsbeta2-])
Using 2000-04-04-13m15 commercial build NT 4.0
Accessing secnews and opening one of the password protected groups, I'm asked
for a user/password combination twice: once when downloading headers/opening
group and again when selecting a message/downloading body.
1. Migrated a 4.x profile with "secnews" secure NNTP server configured and
netscape.champions.beta subscribed.
2. Opened seamonkey to mail window, opened the secnews server hierarchy and
selected newsgroup netscape.champions.beta.
A set of user/password dialogs appeared for newsgroup authentication.
I provided proper authentication combo.
News message headers downloaded and appeared in thread pane.
3. I selected a message in the thread pane.
Result: a second authentication dialog appeared. Should only ask once per
session.
Note: I thought I'd already submitted a bug about this awhile ago for
authentication against non-secure servers, but I can't seem to locate it. So I
apologize if this is a duplicate.
Assignee | ||
Comment 1•25 years ago
|
||
yeah, I've seen this too. probably has to do with the uri's I generate when
talking to single signon. marking m16. not an m15 blocker.
accepting.
Status: NEW → ASSIGNED
Target Milestone: --- → M16
Comment 2•25 years ago
|
||
Triage to M17. Please add beta2 keyword if this must make beta2. Please let me
know if this must be done by M16 feature freeze.
Target Milestone: M16 → M17
Comment 3•25 years ago
|
||
Mail Review recommends beta2 stopper. Adding nsbeta2 keyword.
Keywords: nsbeta2
Putting on [nsbeta2-] radar. Not critical to beta2.
Keywords: nsbeta3
Whiteboard: [nsbeta2-]
Is this the same as 46118?
- per mail triage
Whiteboard: [nsbeta2-] → [nsbeta3-][nsbeta2-]
Target Milestone: M17 → M18
46118 was logged by Karen for a situation where she was prompted for
authentication on reading each message. This one is less severe than that case.
Being asked twice for authentication is bearable, being asked N times is not.
Assignee | ||
Comment 11•24 years ago
|
||
clearing milestone, m17 and m18 are meaningless now. these need to be triages
along with the rest.
Target Milestone: M18 → ---
Blocks: 98033
Comment 12•22 years ago
|
||
isn't this a dup of 96896? how many votes does this news authentication bug
need to get to be given any kind of priority?
Comment 13•22 years ago
|
||
During a typical newsreading session (with about 30 subscribed groups), I get
asked for this prompt multiple times, despite the fact that I'm clearly already
authenticated (if I back out and close the news server's foldout and reopen it,
it rescans for new headers without prompting), and also despite the fact that
I've marked it as a password to remember. It may be considered a low-severity
bug, but it basically makes it impossible to read news on a server which
requires authentication.
Comment 14•22 years ago
|
||
This appears to be a duplicate of bug 36816. Can we mark this as a duplicate?
Comment 15•21 years ago
|
||
Comment 16•21 years ago
|
||
I've run into a related problem: I've got two DSL connections --- one primary
and one backup. My primary is down with some line quality problems. The news
server that I use authenticates based on IP address, but falls back to a login.
Since I'm using the backup DSL (with a different ISP), I get prompted for a
password about every 5-10 minutes *even though I'm not trying to read news*!
And there doesn't seem to be a way to shut it off. *Extremely* annoying... I'm
running Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925
Comment 17•20 years ago
|
||
*** This bug has been marked as a duplicate of 36816 ***
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•