Details
Major Description
There are some crypto caching issues in the WS-Security code relating to the AsymmetricBinding. Under certain circumstances, the outbound crypto loading (for signature) does not get cached properly, which means that the inbound WSHandler cache ends up with two signature Crypto instances, one of which is never used after the first iteration. In addition, it leads to some unnecessary creation of new Crypto instances after the cache hit fails.