A clickonce deploy fails when both SSL is enabled and "require client
certificate" enabled on the deploy server.
The deployment seems to fail only because the client would normally require
a prompt that their certificate is being accessed (a function of the security
setting on the issue of the certificate)
While it is logical for the deployment to fail for other warning prompts
(such as SSL server certificate name not matching or invalid), it would seem
that ALL prompts kill the deployment, even this one which is not a warning,
but in fact a verification of something correctly happening.
a) was deployment failure on any prompt intended by microsoft, (even valid
prompts), or is this user prompt just caught up "incidental ly"
b) are there any plans to allow/fix this in the future?
c) I can work around by using windows authentication over SLL rather than
certificates for deployment, but this rather defeats the purpose of having
certificates in the first place. Doe anyone know of a better workaround?
Regards, Andrew
certificate" enabled on the deploy server.
The deployment seems to fail only because the client would normally require
a prompt that their certificate is being accessed (a function of the security
setting on the issue of the certificate)
While it is logical for the deployment to fail for other warning prompts
(such as SSL server certificate name not matching or invalid), it would seem
that ALL prompts kill the deployment, even this one which is not a warning,
but in fact a verification of something correctly happening.
a) was deployment failure on any prompt intended by microsoft, (even valid
prompts), or is this user prompt just caught up "incidental ly"
b) are there any plans to allow/fix this in the future?
c) I can work around by using windows authentication over SLL rather than
certificates for deployment, but this rather defeats the purpose of having
certificates in the first place. Doe anyone know of a better workaround?
Regards, Andrew