Hello everyone, I'm implementing a WebDAV server for an iECM system in JavaEE and am struggeling with Windows 7 and it's negotiate authorization. I'm trying to map my WebDAV server as a network drive via Windows Explorer. The communication with the server is SSL protected so using basic authentication should be fine. In Windows XP everything works out fine, I'm sending a 401 response with www-authenticate basic realm="Control Panel" to tell the client to use basic authentication. The user-agent header in Windows XP says "Microsoft Data Access Internet Publishing Provider DAV" while Windows 7 (Ultimate) says "Microsoft-WebDAV-MiniRedir/6.1.7600". I have already changed the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters\UseBasicAuth to 2 but Windows 7 keeps sending negotiate authorization instead of basic authorization. This is the header I'm getting when connecting via Windows 7: authorization: Negotiate TlRMTVNTUAABAAAAl4II4gAAAAAAAAAAAAAAAAAAAAAGAbAdAAAADw==. So is there any way to force the Mini-Redir client in Win 7 to use basic authentication? Best regards, Susanne

After some more research and work, this really seems like a bug in the microsoft webdav client to me. Everything works as expected in Vista and XP and every other webdav client I've tested so far, only W7 rejects the basic authentication (https as well as http). changing the registry value seems to have no effect at all in w7. I hope this bug will be fixed with the upcoming SP1 for W7. Best regards, Susanne

Hi Susanne, Please try the following method: Some Info around WebDAV content access issues Hope this helps. Thanks. Nicholas Li - MSFT

Hi Nicholas, thank you for your reply. As mentioned in my first post, changing the registry value in Windows 7 has absolutely no effect. And should not be neccessary since I'm using Basic authentication via https. So I guess I'll have to wait for W7 SP1 and see if that fixes the issue. Best regards Susanne

Hi Susanne, Thank you for your update. I just noticed the key “UseBasicAuth” in your post is different from the “BasicAuthLevel” in the article I provided. Meanwhile, I have reported this issue. If there is any update, I will let you know. Thanks again!Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

hi nicholas, I see what you mean, I really wrote "UseBasicAuth", but I meant to write "BasicAuthLevel". Neither of those registry entries works, tho. It seems like they're just completely ignored. Thanks for your update tho and I'm looking forward to SP1! Best regards Susanne

I am also seeking a resolution to this bug. It was fixed for Windows Vista but apparently the Vista and Windows-7 teams didn't communicate with one another (enough) so this got missed in 7. Here's the Vista fix: KB907306 Here's a "fix" that is supposed to apply to Windows 7 x32 and x64 but there is no msu for Windows 7 available at the download location: April 13, 2010 Hotfix Is there some at MS who could look into this rather than relying on clients to hound the moderators ad nauseum until someone starts to care? This bug is over a year and a half old and the MS techs keep offering "solutions" that don't work rather than saying "It's a bug that we're not working on."

I am also having this issue. My setup is a RHEL 5.4 server running Apache 2.2.3 with Web Dav configured with basic authentication but using LDAP. The authentication must be done over SSL. While I can successfully connect to this service with Linux, Mac OS X, Windows XP, and even Windows Vista I can't get this to work well under Windows 7. I went through all sort of posts and have tried many things and so far the only thing that leads to any sort of success is to change the following registry entry: HKLM\SYSTEM\CurrentControlSet\Services\WebClient\Parameters\ServerNotFoundCacheLifeTimeInSec = 0 This allows me to setup the shortcut and use it until I either log off or restart. Once I restart and click on the shortcut created I just get prompted to authenticate that fails with a "Windows cannot access ..." error. The funny thing is if I create another shortcut then both of the shortcuts work during that login session. This is beyond frustrating and I can't understand why it's not fixed yet.