vankozhi

I have a WCF service hosted in HTTP. On the other end this service needs to be consued by Java based client. They use Axis 1.1 as their SOAP stack.

Since Axis 1.1 doesnt support basic profile, I have created a custom binding with secure transport, certificate over transport and soap 1.1 textmessage encoder. Client security header is coming with namespace 'http://schemas.xmlsoap.org/ws/2002/04/secext' whereas the service can accpet only 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd'. After this is pointed out now client team is sending Security xmlns is corrected. But again service is throwing System.Xml.XmlException while parsing security field 'BinarySecurityToeken'.

The error is 'Cannot read the token from the 'BinarySecurityToken' element with the 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd' namespace for BinarySecretSecurityToken, with a 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v1' ValueType. If this element is expected to be valid, ensure that security is configured to consume tokens with the name, namespace and value type specified'.

Even after the xmlns and value types are changes to the once which service can accept still the same error is thrown. Can I get some help in this regard to get rid of this

Also, while reading some material in web, found like axis 1.1 has some WS security version 1.0 whose status is not release version, whereas WCF supports only upto WS security 1.0 release version. So is it possible to change the client headers by hardcoding and making this work

Thanks,

Vankozhi.



Re: Windows Communication Foundation (Indigo) wcf custom security binding

Allan-Nielsen

hi,

hmm, that certificate you are using, was that generated by the dark side (java) with the keytool.exe...as I remember this, it only generates x509v1 certificates where as ws-security 1.0 only supports x509v3, which might be what this error here is about.

this is just my 2 cents here

Allan





Re: Windows Communication Foundation (Indigo) wcf custom security binding

Scott Seely

Also, have you tried tracing(http://msdn2.microsoft.com/en-us/library/ms733025.aspx) You can get some pretty detailed information about why ServiceModel is throwing from tracing. It could confirm Allan's idea.






Re: Windows Communication Foundation (Indigo) wcf custom security binding

vankozhi

Thanks Scot and Allan. The error string I gave above is from the tracelog. Message log didnt show anything. I now feel it coul dbe because of WS security version mismatch between Axis and WCF. But not getting enough proof for that.

Vankozhi.