branded00
asked on
Securing a ClickOnce Deployment
I am trying to secure a ClickOnce deployment - the publish page, specifically.
I would like to use Integrated Windows Security. When I set this up, the user can get to the publish page fine after being prompted for their domain/username/password, but the installation will fail because I guess the app looks at the users original credentials instead of the ones they were just prompted for and they get an "Unauthorized" error.
Is there a way to fix this? If not, what would be a good way for securing this (that is easy to administer) so that the user is validated before they can access the publish.htm page?
I would like to use Integrated Windows Security. When I set this up, the user can get to the publish page fine after being prompted for their domain/username/password, but the installation will fail because I guess the app looks at the users original credentials instead of the ones they were just prompted for and they get an "Unauthorized" error.
Is there a way to fix this? If not, what would be a good way for securing this (that is easy to administer) so that the user is validated before they can access the publish.htm page?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Deploying the client certs was the only way we could do it.
Cheers.