soapui VS postman-app-support

Let's first try the service manually. We will use the SoapUI testing tool. After importing the WSDL, test requests are automatically created. There are two versions of the "SOAP binding" imported from the WSDL. We will use the newer one, SOAP 1.2. We just need to substitute the input number in the place of a question mark and we can invoke the web service:

SoapUI

There are plenty of tools for stress testing, read RapidAPI, paw, SoapUI, Postman, rest-assured, JMeter and so on! I'm sure they are amazing, however that's all big and heavy, slow, sometimes paid tools!

SoapUI: https://www.soapui.org/

SoapUI from SmartBear is a popular tool that gives you a great graphical UI for navigating through a WSDL. Popping open any operation gives you a sample request that you can fill in and execute from within their app:

I found SoapUI when I had to develop some SOAP services, but these days it also does REST etc just fine.

For someone like me who just does this occasionally I found it rather useful.

[1]: https://www.soapui.org

Eclipse IDE (IntelliJ when I have to depending on the team) (oh and I use the Eclipse package download site, not the installer) Bash shell (WSL on Windows) Gnu CLI commands Dbeaver (although I tend to use the version in the repos) MySQL Workbench (although I tend to use the version in the repos) Meld (like it better than any other comparison tool for ad hoc visual file compares) Apache JMeter (performance testing) (I tend to download and run manually instead of the one in the repos) GIMP Wireshark (great for figuring out why someone's fancy REST client isn't passing JSON correctly) SoapUI (or Postman depending on the team, I prefer SoapUI - which does REST)

SOAP

Do you have any details on the equivalent Postman change? How long ago did Postman force users to create an account? I found this github issue, but I'm not sure if it's what everyone keeps referencing.

https://github.com/postmanlabs/postman-app-support/issues/12...

Possibly user agent add it to postman https://github.com/postmanlabs/postman-app-support/issues/3827

As you can see, this solution worked as expected, but it still has a big concern. The idea of using user email and checking their permission will not prevent malicious people from using an admin email, which can be easy to get with social engineering, and use programs like Insominia or Postman to get the same response as an unprotected endpoint.

You have installed Postman.

Learned about curl https://curl.se/ and played around with postman https://www.postman.com/ some more.

Postman installed

The JWT authorizer is ready to use! We can use Postman or curl to test the endpoint and the authorizer.