×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
so maybe Walden will speak up and provide insight
I've not done this either, as I don't really see the point in
client-certificates, especially not for inhouse-to-inhouse webservice
calls. First, I'd guess that the outside world doesn't even have direct
access to your i, so they can't call the webservice on the i anyway.
Second, if you want to "authenticate" the call, just include a
shared-secret in the webservice definition. Instead of:
Claim[] claimList = WebServiceCall(
int CustomerNumber,
DateTime ClaimsAsOfDate);
make the call:
Claim[] claimList = WebServiceCall(
string SharedSecret,
int CustomerNumber,
DateTime ClaimsAsOfDate);
If you know the shared secret then you can call the service, if you
don't the service dies.
If you're concerned about someone getting access to the shared secret,
then you should also be concerned about someone getting access to the
private keys of the client certificate.
Anyway, if you need to get client certs to work on a webservice call
from .NET, I'm sure you'd get 10 examples in 30 seconds on
codeproject.com
-Walden
midrange.com
