milkman VS postman-app-support

- https://insomnia.rest/ - https://hoppscotch.io/ - https://github.com/karatelabs/karate - https://github.com/warmuuh/milkman

There certainly are plenty of Postman alternatives out there, one that I've used before is Milkman: https://github.com/warmuuh/milkman

It's built on a plugin architecture, does gRPC, GraphQL, JDBC, Ws, et.al. Other plugins allow sharing of workspaces to various services. Written in Java/JavaFX, brew or chocolatey install.

I built milkman[1], an alternative to postman because I wanted one tool to integrate with the whole web development stack. One tool that contains my SQL, rest and grpc calls to easily debug issues. Also nearly none of those kind of tools that existed supported SSE which I also use in my day to day work.

[1] https://github.com/warmuuh/milkman

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.