Jari,
some time ago (about two weeks) we had some dicussions about this
topic. This patch fixes a problem that WCF generates, IMHO only if
WSS4J is at the receiver. What if WSS4J is the sender? Does WCF
also require a namespace in this case also? WCF incorrectly
attaches a Namespace to the Type attribute (refer to OASIS WSS
specifications - Usernametoken Profile)
Regards,
Werner
Jari Fredriksson schrieb:
WCF uses namespace prefix for Password Type, and the current WSS4J does not
like it.
Dunno if it is WCF which is broken, but I had to roll my own wss4j.jar with
following addition to UsernameToken.java
passwordType = elementPassword.getAttribute("Type");
144,146d143
< if (passwordType == null || passwordType.length() == 0) {
< passwordType = elementPassword.getAttributeNS(WSConstants.WSSE_NS,
"Type");
< }
Would be great if the official build had this or similar solution.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
