Security Headers incomplete
Hi, I'm having an issue with WS-Security in the SoapUI plugin for Netbeans, version 2.5.1 on NB 6.5. My web service is configured to use username tokens with passwordtext. I have a couple users w...
Forum Discussion
After further testing, I'm leaning towards the null-values-in-the-password-box hypothesis. I tried it on a new project with the same security system. This time, in the project's outgoing WS-Security Configurations, I set up a single Usernametoken configuration (see attached) and did not touch the default password box.
The first time I sent a request, I got the same header problem. I closed the request, double-clicked in the "default password" box (see attached), and then pressed "enter".
I then re-opened the request, re-selected the "root" authentication and sent the request. It worked correctly this time.
I then tested with a fresh SoapUI project. This time I double-clicked the "default password" box and hit "enter" as soon as I created the outgoing ws-security configuration. The request worked correctly the first time I tried it.
I'm going to file a bug report for this.
The first time I sent a request, I got the same
I then re-opened the request, re-selected the "root" authentication and sent the request. It worked correctly this time.
I then tested with a fresh SoapUI project. This time I double-clicked the "default password" box and hit "enter" as soon as I created the outgoing ws-security configuration. The request worked correctly the first time I tried it.
I'm going to file a bug report for this.
