Open
Bug 383393
Opened 18 years ago
Updated 21 hours ago
NTLM trusted URIs ignored
Categories
(Core :: Networking, defect, P5)
Tracking
()
NEW
People
(Reporter: justinmozilla, Unassigned)
Details
(Whiteboard: [ntlm][necko-would-take])
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en) AppleWebKit/522+ (KHTML, like Gecko) Safari/419.3
Build Identifier: 2007060502
The network.automatic-ntlm-auth.trusted-uris key (accessed via about:config) is ignored in Camino, so even though I have entries there for certain sites, I am prompted for login information. This key works correctly in Firefox with the same settings, allowing me to specify trusted sites that will not prompt me for login unless my stored information authentication fails.
When the prompt appears, it is prepopulated with my correct username and password; it is an annoyance, however, to have to confirm it the first time I open any of these sites for the first time since opening the browser.
Reproducible: Always
Steps to Reproduce:
1. Add a site that uses NTLM authentication to the network.automatic-ntlm-auth.trusted-uris key via about:config
2. Visit that site and enter the correct credentials, storing them with the built-in password manager.
3. Close the browser.
4. Open the browser and visit the site again.
Actual Results:
I am prompted for username and password even though I've set the site as a trusted site.
Expected Results:
I should not be prompted for a username and password since they are stored in the password manager and I have designated the site as a trusted site.
This has been a problem as far back as version 1.0.
Stuart, is this a Keychain issue? It sounds a bit like the httpAuth code path here.
Comment 2•18 years ago
|
||
I looked a little, and it wasn't clear to me whether the expected behavior from the standpoint of the keychain code is that this should be handled there (i.e., at the individual app level), or the code to show a prompt should never be called at all. I would tend to think the latter, but I'd need to find someone who understands how the NTLM system works to know.
Comment 3•17 years ago
|
||
Should we go ahead and confirm this as "something we should fix at some point" while we're trying to figure out exactly what needs to happen to fix it?
Comment 4•17 years ago
|
||
Yep, that makes more sense than leaving this in limbo.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 5•17 years ago
|
||
i can confirm this bug still exists in FF3 beta 5.
changing product from camino to core since this isn't an issue in camino alone.
Component: Preferences → Networking
Product: Camino → Core
QA Contact: preferences → networking
Version: unspecified → Trunk
Comment 6•17 years ago
|
||
The original report was that it worked in Firefox. Are you sure you aren't seeing a similar but unrelated regression?
Comment 7•17 years ago
|
||
pretty sure, yes.
it's working on windows (in FF2 and FF3b). but not on OSX.
tried multiple times to get it to work, even the suggested "null" entry for trusted uri's.
i have a NTLM secured intranet
https://intranet.domain.net
while setting
"intranet.domain.net" in about:config
FF on windows just logs me in
FF on OSX always shows the login dialog (with prefilled user/pass as soon i've successfully authenticated before)
while all you need is to push ok, this is really annoying in everyday use.
Updated•9 years ago
|
Whiteboard: [ntlm][necko-would-take]
Comment 8•8 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•