Comment #22 on issue 6824 by iambob: No logon prompt for "Integrated Windows Authentication" (NTLM) only sites http://code.google.com/p/chromium/issues/detail?id=6824
@krtulmay, Well, when I said "NTLM had been implemented for a while" I was speaking from a user-perspective, not a developer-perspective. As far as USERS are concerned... Chrome had a feature, then suddenly lost it. If the feature was never intended, the developers should have been careful enough to disable it so that users didn't start relying on it. As it stands, I switched to using Chrome 99% of the time when it started becoming a bit more stable. Then, when NTLM authentication was lost, I have been forced to using Chrome 80% of the time, with Safari the remainder of the time. If the developers always knew that NTLM authentication would go away, it would have been much nicer to communicate this to users ahead of time. Adding new features without informing the users is one thing. Deprecating features and apologizing to users is another. Taking away features and then explaining to users "it wasn't supposed to be there for months to begin with." That's just irresponsible. And if issue 19 started out being related to NTLM authentication through a proxy, it should remain that. Allowing one issue to slowly morph into another problem altogether makes an issue system entirely pointless. It would allow issue 19 to be closed with the explanation "we don't plan on supporting NTLM authentication through proxies," leaving the separate issue of just "NTLM authentication" ignored. It creates confusion. If issue 19 changed once, who is to say it won't change again? This also means that if the meaning of issue 19 changes again, all other issues that were merged into it could be lost forever, needing to be entered again, and starting the cycle of merging unrelated issues and allowing issue-creep to continue forever. Again, I see where you're coming from. I now see that NTLM authentication was never intended. I now see that NTLM authentication is not at the top of the list. I now see that NTLM authentication was accidentally left in and was finally removed, as part of switching to its own HTTP stack. I get all of this. But it now means that Chrome, which once had a feature that Firefox, IE, and Safari have... is now missing a feature that the other three significant browsers continue to support. I recognize that Chrome is not meant to be "just another browser"... but at some point, wouldn't the goal be to make Chrome compatible with sites that people frequent? One such type of site is an Intranet, even though it isn't ONLY Intranets that necessarily use NTLM authentication - it is the more common scenario. Even if there could be a command-line switch, allowing Chrome to alternately use WinHTTP. I would much rather run a more current version of Chrome with more up-to-date security patches and other improvements, but with WinHTTP for NTLM authentication... than have to be stuck using an out-of-date version of Chrome just so that I don't have to keep thinking about which browser I am going to use in different circumstances. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
