WCF services deployed win2016 under IIS,
Certificate is generated, in command and in IIS are tried,
The client, the server by way of message authentication, X509 certificate, the configuration file is used to implement the ABC
Now use the browser to access the service. (SVC), total tip: no access,
IIS application pool flag is set, network service, private key certificate has given the network service read permissions

CodePudding user response:

[ArgumentException: certificate "CN=testCer1" must have to exchange the key to the private key, the process must have permission to access the private key,

CodePudding user response:

[how: make the x. 509 certificate can be accessed by the WCF]
https://docs.microsoft.com/zh-cn/dotnet/framework/wcf/feature-details/how-to-make-x-509-certificates-accessible-to-wcf

CodePudding user response:

@ brothers on the second floor, these are tried, can't,
Note is in win2016, 64 - bit
Which brother have time to study, more urgent, more points or pay can also, can contact in private

CodePudding user response:

A detour, eventually failed to past the snag
Find a lot of company, the lowest 3 k, but did not say must be able to solve
Why WCF wasn't popular, configuration of trouble, slow, security is not enough, or what the reason, the old drivers about
You run into C/S projects, what kind of framework, with the socket?