RE: WSE and SSL
- From: "RG" <RG@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 14 Jun 2005 09:07:11 -0700
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
.
- Follow-Ups:
- Re: WSE and SSL
- From: Dilip Krishnan
- Re: WSE and SSL
- References:
- WSE and SSL
- From: RG
- RE: WSE and SSL
- From: MAHESH MANDHARE
- WSE and SSL
- Prev by Date: WSE 3.0 and SecureConversation
- Next by Date: WSE3 Transport Independence On Consumer-Side
- Previous by thread: RE: WSE and SSL
- Next by thread: Re: WSE and SSL
- Index(es):
Relevant Pages
|