bobkaine thatsthat - I've just had and sorted the issue we were having, hopefully this helps you too.
Before 3.4.0 the combination of request properties and environment managed the attributes to set the WS-Security attributes you needed. Since the upgrade you now need to set that in the WS-Security config. For our API it meant I needed to add a new entry in Outgoing WS-Security Configurations for every application credential for every environment and I added in just the Username attribute so it could take that username, password, nonce, password type and must understand which were the attributes our application wanted.
This is the documentation from readyAPI on how to add the WS-Security attributes.
Fyi .. this 'problem' is fixed in the next release of Ready API 3.5 which will come out in a week's time. I never implemented the solutions proposed by you (i am confident they would work!) as I am not advanced enough to get it going .. good news the software will handle this again natively.
