RE: Rampart: sp:HashPassword does not require receiving a hashed password

Hi Ruchith, Thanks for your quick response. I was halfway through writing my own patch to 1.6.2 in that exact area of the code :) I have instead applied your changesets to my working copy of the Rampart source. However, I'm having a problem with the following code: } else if (wssUt.getP

Re: Rampart: sp:HashPassword does not require receiving a hashed password

Hi Nathan, IMHO you are correct that the fix should be in PolicyBasedResultsValidator and I believe this is fixed in the latest rampart trunk [1], [2], [3]. Please try the latest rampart trunk. Please do file a bug and provide a patch if these fixes are not sufficient . In the case of previous re

Rampart: sp:HashPassword does not require receiving a hashed password

Hi, I'm new to Rampart and I've been experimenting with UsernameTokens. My policy file contains the assertion. However, when receiving a wsse:Security header, Rampart is allowing a plain text password. From the WS-SecurityPolicy 1.2 spec: http://docs.oasis-open.org/ws-sx/ws-securitypolicy/

Build failed in Jenkins: Axis2-trunk-java-1.6 #1565

See -- [...truncated 3766 lines...] [INFO] [INFO] --- maven-enforcer-plugin:1.1:enforce (default) @ axis2-xmlbeans --- [INFO] [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ axis2-