Forum Discussion
Hi Jmalvin,
I’ve tried to reproduce the behavior you described in Ready! API 1.5 – everything works fine on my computer. I remember a similar issue in one of the previous product version. I think you faced the same. I suggest that you consider updating your Ready! API version.
Tanya,
After several conversations with some of the reps, this seems to be a known internal bug to the development team which has not been resolved in Ready! API 1.5. If you attempt to create multiple username outgoing-WSS entries, and have the requests set the authorization/authentication manually or via Auth Manager (new in Ready! API but not in SoapUI Pro), it always selects the first one from the list after the project is saved and reopened/reloaded (basically, it does not retain the appropriate Authorization entry for the test suite, test case (via inheritance), or request level).
We have no other choice at this point to fall back to SoapUI Pro versions.
Related Content
- 3 years agoMarkSchofer