System.Web.Services.Protocols.SoapHeaderException: System.Web.Services.Protocols.SoapHeaderException: Server unavailable, please try later ---> System.Configuration.ConfigurationException: WSE535: The following SecurityToken QName is unsupported: http://schemas.xmlsoap.org/ws/2005/0...erivedKeyToken.

I've developed a Web service secured with WSS4J. The client is a .NET
client using WSE. I'm using X509 tokens and the current configuration
works fine since early CVS releases of WSS4J. I recently upgraded to
1.5.0 and my java clients works fine. But the .NET client stopped
working with this message:

Message "WSE535: The following SecurityToken QName is unsupported:
http://docs.oasis-open.org/wss/2005/...reConfirmation.
Please check your configuration for registered SecurityToken qnames."

It seems to me that the new version works in WSS1.1 compliance so
following the specification sends the SignatureConfirmation. .NET is not
1.1 compliant so it doesn't expect that element.
I think anyway should exists a way to force WSS4J work in 1.0 mode
anyway, or to be backward compatible.

Hello,
I am not sure .NET is wss11 compliant or not, but the wss11 namespace used
by WSS4J is outdated. The new namespace is: "
http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1"
I think this needs correction in WSS4J.

Thanks,
Ashutosh

I resolved setting ENABLE_SIGNATURE_CONFIRMATION to false. I think it's
wrong that WSS4J enables it by default since it's still based on
outdated specs..