35832 - implement news push-auth: "always use name and password"

Status: VERIFIED DUPLICATE of bug 39862

(MailNews Core :: Backend, defect, P3)

Description

[(not reading, please use [e-mail] instead)]

I just got an account on supernews.

in mozilla, we store the username / password per group.  for supernews users
(and others, I'm sure) the username / passsword is the same across all groups,
and you need it to log in.

so, when asked for a username and password for a group, I should try to use the
server's username and password first, if their is not username / password stored
for the newsgroup yet.

Comment 1

[(not reading, please use [e-mail] instead)]

in case I wasn't clear, the problem is I have to enter my username and password
the first time I visit a group.  ideally, should only have to enter it once.

Comment 2

[(not reading, please use [e-mail] instead)]

adding two other supernews users to the cc list.

Comment 3

[laurel]

Don't we usuallly do that (in 4.x) when we have the news server option "always
use name and password" turned on (which I don't believe you've implemented yet?

Comment 4

[(not reading, please use [e-mail] instead)]

thanks for the info laurel.  that will solve the problem.  changing subject.

Comment 5

[(not reading, please use [e-mail] instead)]

actually, "always use name and password" is really pushed authentication, and 
that's something else.

pushed auth means:  
1)  don't store the password in the single singon database
2)  before every action, ask the user for the username / password

I'll open a new bug for the original problem, and leave this as the push-auth 
bug. 

Comment 6

[(not reading, please use [e-mail] instead)]

moving to m18. accepting.

Comment 7

[Karen Huang]

From bug 39862, it seems that push-auth is not going to make it for 6.0, so need 
to move to other milestone or dup of bug 39862?

Comment 8

[laurel]

mass change of huang's news bugs to stephend.

Comment 9

[(not reading, please use [e-mail] instead)]

clearing milestone, m17 and m18 are meaningless now.  these need to be triages
along with the rest.

Comment 10

[Aleksey Nogin]

The back-end support for "always authenticate" was just checked in - see bug
39862. The UI for this is still missing - see bug 94439. For now, people can get
"always authenticate" by editing preferences manually.

*** This bug has been marked as a duplicate of 39862 ***

Comment 11

[[e-mail] (gone - use [e-mail] instead)]

verified dup.