when invoking a secured webservice the specified
credentials are cached internally by HttpClient. This
leads to problems if multiple requests to the same
endpoint are configured to use different credentials
(which are thus not used)..
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The problem still exists in soapUI 2.5.1 and 3.0.1. The username and password seem to be cached. This is a very annonying bug when working with different services wich require different username/password combinations.
Only when you wait for a certain time (the cached items seem to time-out after a few minutes) OR when stopping/restarting soapUI, the newly entered username and password become active.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also see thsi behavior in SOAPUI 5.0.0. I have several projects. I just created a brand new REST project, added no Authorization to it, and yet as I step through my code I see username and password from past requests I had run during testing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1312539
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
Logged In: NO
We have experienced this problem and have also found that NTLM Credentials in some cases are not passed (even when configured).
Logged In: YES
user_id=838515
Originator: YES
ok.. which soapUI version are you experiencing this with?
regards!
/Ole
eviware.com
The problem still exists in soapUI 2.5.1 and 3.0.1. The username and password seem to be cached. This is a very annonying bug when working with different services wich require different username/password combinations.
Only when you wait for a certain time (the cached items seem to time-out after a few minutes) OR when stopping/restarting soapUI, the newly entered username and password become active.
I'm still seeing this issue in SOAPUI 5.0.0 version. Is there a fix for this by changing preferences or anything similar?
Thanks.
I also see thsi behavior in SOAPUI 5.0.0. I have several projects. I just created a brand new REST project, added no Authorization to it, and yet as I step through my code I see username and password from past requests I had run during testing.