Forum Discussion
tdrury
13 years agoContributor
We've partially solved the issue. We were specifying username and password in the maven configuration which we now realize was an override to all username/passwords for all requests. We've removed the username and password parameters from the maven configuration.
This opened up a bunch of new issues.
Nearly all of our request test steps do not specify a username or password. We assumed that the username and password specified at the endpoint would be used in this case - and this seems to be the behavior in the GUI. However, when running the tests via maven, no username or password is being sent with the request unless we explicitly set them at the request level.
I tried adding our soapui-settings.xml (which specifies preemptive authentication) to the maven configuration, but this makes no difference.
So the question is: is this the correct behavior? I don't want to have to repeat the service endpoint username and password for each request in the test. When running via maven, I want the service endpoint username and password to be preemptively sent with the request.
This opened up a bunch of new issues.
Nearly all of our request test steps do not specify a username or password. We assumed that the username and password specified at the endpoint would be used in this case - and this seems to be the behavior in the GUI. However, when running the tests via maven, no username or password is being sent with the request unless we explicitly set them at the request level.
I tried adding our soapui-settings.xml (which specifies preemptive authentication) to the maven configuration, but this makes no difference.
So the question is: is this the correct behavior? I don't want to have to repeat the service endpoint username and password for each request in the test. When running via maven, I want the service endpoint username and password to be preemptively sent with the request.