On Thu, 2008-08-28 at 17:00 -0400, Daniel Kulp wrote: > One thing to check: WSS4J is VERY strict about the ordering of the Actions > when reading/processing the message. For example, in my testcase I was > working on this morning, there is a UsernameToken and a Timestamp in the > message. If I use action="Timestamp UsernameToken", it barfed. However, > action="UsernameToken Timestamp" worked fine.
It turns out that this was exactly the case. In my Spring configuration, this line: <entry key="action" value="UsernameToken UsernameTokenSignature"/> should be: <entry key="action" value="UsernameTokenSignature UsernameToken"/> I followed Dan's advice and stepped into the checkReceiverResults method and saw that while both expected results were there, they were in the incorrect order. The new ordering strikes me as counter-intuitive, but at least it works. Next up: encryption via the same method. Thanks for the help! -Steve
