Re: WSE and SSL

Adding ssl support has nothing to do with web service implementation. All you need to do is get a valid certificate and change the settings in IIS to make the web application use ssl.
What is the error you are getting?


RG wrote:
Yes, the web service supports password hashing. The service works fine when the calling application requests using HTTP. But it does not when HTTPS is enabled.
Any suggestions on how to get it working? Are there any examples/sample codes that would implement like a Hello World service in HTTPS?

Thanks

"MAHESH MANDHARE" wrote:


hi RG,
you are calliing web service from client app using sendhashed option does your web service supports password hashing if not set this option to sendPlainText
--
Have A Good Day,
Mahesh,
Maheshmandhare@xxxxxxxxxxx


"RG" wrote:


I have created a Web Service (using WSE 2.0, SP3) that has a method ProcessRequest exposed. A client application calls the webservice using the following code.

========================================
Dim loWebService As New MyWebServiceWse

loWebService.Url = "http://www.testwebservice.com/MyTest/MyTest.asmx";

loWebService.AllowAutoRedirect = True
System.Net.ServicePointManager.CertificatePolicy = New CertPolicy

Dim loContext As SoapContext = loWebService.RequestSoapContext
loContext.Security.Timestamp.TtlInSeconds = -1

'Instantiate a new UsernameToken object.
Dim loUserNameToken As New UsernameToken(txtUserID.Text, txtPassword.Text, PasswordOption.SendHashed)

'Add the token to the SoapContext.
loContext.Security.Tokens.Add(loUserNameToken)

'Generate a signature using the username token, 'and add the signature to the SoapContext.
loContext.Security.Elements.Add(New MessageSignature(loUserNameToken))

'Call the Web method.
lsResponse = loWebService.ProcessRequest(rtbRequest.Text)

========================================

This code works fine when the URL is HTTP. But, on a HTTPS call, when the SSL is enabled to this site, It first gives me Security.SecurityFault exception (WSE563) - The computed password digest does not match the incoming username token. Then after that, for the subsequent requests, I get a Destination unreachable WSE816 error - The header must match the value of the incoming message's HTTP request.

How can I get this fixed? Is there anything different that I need to do in the WebService code and/or the Client application code to handle HTTPS request.

Thanks,
R


--
HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dilip.krishnan AT apdiya DOT com
.

Relevant Pages

  • RE: WSE and SSL
    ... the web service supports password hashing. ... the calling application requests using HTTP. ... codes that would implement like a Hello World service in HTTPS? ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: WebRequestMethods.Http.Post XML file on HTTPS
    ... I used fiddler to scan the http and https requests ... and came to the conclusion that the thirdparty application required a custom ... What version of SSL remote peer is supporting now? ...
    (microsoft.public.dotnet.framework)
  • WSDL under SSL from Accelerator
    ... This accelerator forwards requests on port 443 to a webfarm ... They do not know about the SSL. ... Note it does not show https: in the http:address locations. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Calling a web service that is https
    ... I have a web application that doesn't use SSL at all. ... integrate it with another third party web application which only ... web service like any other web service? ... https is nothing but transport layer encryption and webservice ...
    (microsoft.public.dotnet.general)
  • Re: Calling a web service thats https
    ... I have a web application that doesn't use SSL at all. ... How can I connect to a web service that is ... SSL 2.0 and only support 3.0. ... how to configure and use web serivce, which uses HTTPS in diffrent ...
    (microsoft.public.dotnet.framework.aspnet.webservices)