 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / ASP.NET / Web Services / February 2006Quick Start certificate
I have written a simple WEB servcie that I call from a VB app using .net2 and WSE3 The app works perfect with the quickstart certificate I generated by running setup in the samples on my workstation. I have the WEb service running in IE on my xp pro workstation and exported the certificate and restored it on another xp computer and a windows 2003 server. the client program works perfectly on the windows 2003 and xp computers. Is there a way to install the quiclstart certificate on the WEB server so that I can run the WEB service on the WEB server with the quickstart certificate. This server is strictly set up for testing so I do not want to have to purchase a real certificate for it. I deleted the client certificate and ran the setup in samples which did create the certificates on the WEB server. I then exported the new certificate and imported it to my work station as the client certificate. Unfortunately when I try to access the WEB service from my work station I get an error saying that the soap message is invalid. I even tried running the client app on the web server and it would not work. Yes you can install the quickstart cert on the web server for testing. There are a few things that can go wrong and I can't tell from your description, so let me do some quick checks. 1) Did you check the "allow test root" option on the security page for the wse configuration of the client and service app? 2) Did you give your web server identity (NETWORK SERVICE) permission to read the certificate on the server? I think the how to on that is in the wse documentation. It's done through the certificate tool that's installed with wse. 3) can you turn on the tracing on the client app and tell the web service to return detailed information about any faults? then the clients traceinput file should have the info. Alternatively, you can turn on tracing on the web service and inspect those files for the real error messages. Most likely the problem is on the server and the server is returning an error. But the client is expecting a soap message in response but instead is getting an error thrown by the web server. So when you see "invalid soap message" that's just the client saying "hey, I can't make heads or tails of this response". I'll keep an eye out for your results.. julie >I have written a simple WEB servcie that I call from a VB app using .net2 >and [quoted text clipped - 23 lines] > the > client app on the web server and it would not work. When I go to the policy tab and select the config file for the web servcie in the wse settings I get the error The Policy file specified and the current project directory should be the same as the root path. Will this cause an issue? Where do I specify what the root path is. I checked and security is set for the NETWROK SERVICE and allow test root is checked. I have enabled diagnostics on the client and the web service. > Yes you can install the quickstart cert on the web server for testing. > [quoted text clipped - 50 lines] > > the > > client app on the web server and it would not work. Responses inline > When I go to the policy tab and select the config file for the web servcie > in > the wse settings I get the error The Policy file specified and the > current project directory should be the > same as the root path. > Will this cause an issue? Where do I specify what the root path is. JL: What value do you have in there? Can you just try for now to use the default value? That is wsepolicyCache.config > I checked and security is set for the NETWROK SERVICE and allow test root > is > checked. JL: great > I have enabled diagnostics on the client and the web service. JL: So now, just recreate a new policy for the web service and use that for now. Then run the client. After that, look at the TraceInput file for the client app. The last message in there will hopefully have the real error information in it. (One thing to stamp into your brain is to remember to turnoff all of this tracing when you deploy your app into production. It will cause some big headaches!!) ---------------------------------------------------- >> Yes you can install the quickstart cert on the web server for testing. >> [quoted text clipped - 66 lines] >> > the >> > client app on the web server and it would not work. I was able to get the quick start certificate working and I was able to use the verisign certificate after creating a custom user for the web service. Thank you for all your help > Responses inline > [quoted text clipped - 96 lines] > >> > the > >> > client app on the web server and it would not work. excellent news do you know what the problem was? In case someone else has it down the road? >I was able to get the quick start certificate working and I was able to >use [quoted text clipped - 116 lines] >> >> > the >> >> > client app on the web server and it would not work. The code was getting an error during the custom password validation that I wrote. The generic error that came back to the client program was not sufficient to figure out the issue. Once I turned on the debugging in WSE I was able to see the error that the subroutine was actually passing back. > excellent news > [quoted text clipped - 120 lines] > >> >> > the > >> >> > client app on the web server and it would not work. Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.