securityContext causes web service failure(401 - unauthorized) in wse3... why??

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Julie Lerman - 08 Jan 2006 21:17 GMT

Any idea why turning Secure Conversation ON would cause a web service call
never to reach the web service? When secure conversation is off (on client
and service) my web services work perfectly fine. I am not using anything
custom (outside of a custom username token manager). Everything else is set
through the settings tool - policy is a basic usernameoverCertificate.

When I turn SecureConversation, the call to the web service errors out
immediatly and I can see through tracing that the web service is not even
getting hit.

I am doing this against IIS 5 on the development machine.

The error I'm getting when I make the web service call is that the remote
server returned a 401 unauthorized error.

Again - it's all working just peach with secure conversation off, so that
gives me confidence in my x509 certificates, etc.

thanks for any insights

julie

Reply to this Message

Julie Lerman - 09 Jan 2006 02:42 GMT

This makes NO sense to me, but I was setting the ClientCredentials using the
generic method

proxy.SetClientCredential(Of UsernameToken) (myUT)

When I changed this to
proxy.SetClientCredential(myUT)

It worked.

I did have to make a small change to my web service where it was doing
authorization against this usernametoken, but that was nominal.

I blogged about this here:
http://www.thedatafarm.com/blog/PermaLink.aspx?guid=62872ee5-d8b4-470e-98d2-c99c
607f71e8

> Any idea why turning Secure Conversation ON would cause a web service call
> never to reach the web service? When secure conversation is off (on client
[quoted text clipped - 17 lines]
>
> julie

Reply to this Message

securityContext causes web service failure(401 - unauthorized) in wse3... why??

Free Magazines