G
Guest
We are deploying our Smart Client APP to our external vendors via ClickOnce
and an IIS6 virtual directory. Since the deployment is visible to the
Internet, we have protected the deployment site using Integrated Windows
authentication without anonymous access and enumerated the authorized users
in the site's web.config. This works fine until the .application is launched
from the ClickOnce publish.htm page. Then the ClickOnce installer tries to
contact the protected website using the credentials of the logged on user and
not the credentials that the user provided to authenticate to IIS. The result
is an installation failure with "401 Unauthorized" given as the reason. The
"Stored User Names and Passwords" feature avoids this problem in Windows XP
Pro, but doesn't help us for other target operating systems like Windows 2000
and Windows XP Home. Is there a way to tell the ClickOnce installer to run
under a predefined identity? Is they a better way to protect the deployment
site that is more ClickOnce friendly?
Any advice would be appreciated.
and an IIS6 virtual directory. Since the deployment is visible to the
Internet, we have protected the deployment site using Integrated Windows
authentication without anonymous access and enumerated the authorized users
in the site's web.config. This works fine until the .application is launched
from the ClickOnce publish.htm page. Then the ClickOnce installer tries to
contact the protected website using the credentials of the logged on user and
not the credentials that the user provided to authenticate to IIS. The result
is an installation failure with "401 Unauthorized" given as the reason. The
"Stored User Names and Passwords" feature avoids this problem in Windows XP
Pro, but doesn't help us for other target operating systems like Windows 2000
and Windows XP Home. Is there a way to tell the ClickOnce installer to run
under a predefined identity? Is they a better way to protect the deployment
site that is more ClickOnce friendly?
Any advice would be appreciated.