xbap downloaded does not use connection properties of IE for proxy

Question

When I try to visit a xbap, the downloader does not connect through the proxy we have. I think it should?

PLATFORM VERSION INFO
 Windows    : 5.1.2600.131072 (Win32NT)
 Common Language Runtime  : 2.0.50727.42
 System.Deployment.dll   : 2.0.50727.42 (RTM.050727-4200)
 mscorwks.dll    : 2.0.50727.42 (RTM.050727-4200)
 dfshim.dll    : 2.0.50727.42 (RTM.050727-4200)

SOURCES
 Deployment url   : http://www.charlespetzold.com/wpf/JeuDeTacquin/JeuDeTacquin.xbap

ERROR SUMMARY
 Below is a summary of the errors, details of these errors are listed later in the log.
 * An exception occurred while downloading the manifest. Following failure messages were detected:
  + Downloading http://www.charlespetzold.com/wpf/JeuDeTacquin/JeuDeTacquin.xbap did not succeed.
  + The remote server returned an error: (407) Proxy Authentication Required.

Answer 1

I've been told this is a known ClickOnce issue. As a workaround, you can set this in your machine.config file:

<configuration>
    . . .
   <system.net>
      <defaultProxy enabled="true" useDefaultCredentials="true"/>
   </system.net>
</configuration>

Let me know if that helps.

Answer 2

Doesn't help, in my case at least.  Our proxy setup is set to use an automatic config script from a local server if that makes any difference.

Answer 3

We have the same problem here. The suggested solution with the machine.config does not work here eitther. Doesn't the setting  useDefaultAutentication="true" mean that .NET will try to authenticate without a password. Our proxy needs a password.

 

Answer 4

Unfortunately, ClickOnce does not support any kind of manual authentication, whether with a proxy or with a server directly. Only authentication with the user's system credentials is supported.

 

Answer 5

 

To credetials used for our proxy are the same used to to login to the PC/Domain. Are those the system default credetials? If so why does useDefaultAutentication="true" have no effect?

Answer 6

Here's what I got from the ClickOnce team:

1)      Today (Whidbey, Vista, Orcas) ClickOnce only supports Windows Integrated (NTLM, Kerberos) auth. No other auth protocols are supported.

2)      In general, only default account credentials are supported (logon creds). There are some scenarios where ClickOnce has access to IE collected credentials, and the user elects to “Save Password” in the IE auth dialog. Again, only for Windows Integrated Auth.

3)   The workaround with the machine.config file is needed for proxy auth to work before the Orcas release. Alternately, there is a hotfix that can be applied: http://support.microsoft.com/kb/917952/en-us.

 

How does authentication with your proxy work from user's point of view? Do you get a separate auth dialog? If you do, then the proxy may not support Windows Integrated Authentication (NTLM/Kerberos).

Answer 7

Usually I do not get any popups for authentication. However when I watch stream meadia in ie7 in a wmp 11 activex control I actually do get a popup dialog asking me for my credetials. When I enter my default credentials I can watch the streaming media.

 

I tried the machine.config workaround but nothing changes. All our network/server  machines run Microsoft operating systems exclusively.

Answer 8

This has been driving me crazy as well.

 

I tried the machine.config suggestion above ... no luck.

I looked at my version of System.Deployment.dll ... it is a later version than the one in the hotfix: http://support.microsoft.com/kb/917952/en-us.

 

I tried changing my credentials ... but we log in to a domain ... and thus my log on credentials have the following format <domain name>\<login id> whereas my proxy credentials just have the format <login id> ... at least that is my speculation of why it didn't work after I changed my passwords to be the same.

 

Argh. I just want to view .xbap(s) ... I can't believe that this is an issue with ClickOnce! Weren't they aware of proxies? I must be missing something here ...

 

Does anyone have any additional suggestions?

 

Answer 9

 

There is nothing you can do except changing your authentication/proxy policy. And it looks like that won't change in .NET 3.5 (please someone tell me that I am wrong). That's why clickonce deployment/xbap is pretty much worthless for our enterprise and our customers. We can't make our customers change their corporate network setup.

Answer 10

Does anyone know if this fix made it into .NET 4.0??

I can verify that it did not make it in .NET 3.5 SP1