Last post Aug 27, 2013 02:40 AM by Ericzh
Aug 25, 2013 05:35 AM|AlexeySingapore|LINK
I have a secured web-hosted WCF service, based on wsHttpBinding. I need allow access to the service by custom username and password. Also, I need to keep session alive during client communication. Data should be secured as well. What do I use?
<userNameAuthentication userNamePasswordValidationMode="Custom" customUserNamePasswordValidatorType="MyService.Service+CustomUserNameValidator, MyService"/>
<serviceCertificate findValue="www.mywebsite.com" storeLocation="LocalMachine" storeName="My" x509FindType="FindBySubjectName"/>
The main problem is x509 certificate. For the local debug purpose I made self-signed certificate and installed it to LocalMachin "My" store. Then I start my service, passed authentication by custom login and password, and get access to the service functions.
Everything just fine. Then I published this service to my hosting and got a problem. Self-signed certificate can't be used and I need to buy commercial certificate in order to my service work online. Ok, not a problem. I informed my hoster I need certificate
and paid for it. After a while I got confirmation "Your certificate for www.mywebsite.com is successfully installed. Now you can use https". Obviously, I need to modify my web.config file to set right store location and name for boughted certificate. But my
hoster do not understand my question and reply some nonsense "We installed your certificate as Personal".
How to configure web.config file with bought (no self-signed) certificate?
Aug 27, 2013 02:40 AM|Ericzh|LINK
About this situation, you could refer to the following links for further information:
Besides, you could get furhter help from the below forums: