Closed Bug 30223 Opened 26 years ago Closed 26 years ago

Multiple confirmation request for firewall realm username and password

Categories

(SeaMonkey :: Passwords & Permissions, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 24329

People

(Reporter: howdens, Assigned: morse)

References

()

Details

When access Internet URL through a proxying firewall I am seeing repeated request to confirm the username and password for the firewall realm I am prompted for my cache password and the realm username presented in the confirm dialogue is correct, obviously I can't see what is in the password field but if I click OK it works so it must ave the correct value. The realm name isn't changing I don't have to re-enter the username and password just click OK for every HTTP request = basic page + each frame + each graphic (very painful!!) I have tried re-entering the username and password into the dialogue - no change (yes I can enter a password, there is no problem there) The usename and password are obviously being accepted and passed through to the firewall because if I sit and click OK enough times then I do get the full page. I have tried with, and without, the "Save these values" checked - no change This is really a big blocker in using Seamonkey as my everyday browser, becuase accessing any Internet site requires numerous OK's Ideally having supplied my cache password I wouldn't want to see any confirmations for the firewall realm username & password, unless there was a failure due to a password expire. I am using build 2000030215 on NT4 SP3 This really needs to be fixed before beta1 for corporate users. This had been fixed at one time (albeit with a single confirmation being required), but re-appeared about 10 days ago ago. (Sorry don't have the build numbers).
You've already filed this bug (you probably forgot) -- it was bug report 29204. Now that bug had been marked as a dup of 24329. And bug 24329 had been erroneously closed out as a dup of 27784. I've just reopened 24329 that bug and severed it from 27784. Marking this bug as a dup of 24329. *** This bug has been marked as a duplicate of 24329 ***
Status: UNCONFIRMED → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
over to tever to verify. :-)
QA Contact: sairuh → tever
dupe of 24329
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.