I was able to access the Postman Agent running on other machines. This can be done by making a user with Postman agent visit a malicious website. The website can then make requests from the userās postman agent. This can be used to make bulk requests from the userās machine without the userās knowledge.
If you want to discuss this, you can DM me on twitter @jojimail
Postman for mac is great for you and how you develop or consume APIs in isolation, but the web edition would give you a URL for each collection, or down to individual requests that can be run within a well defined workspace, with accompanying environment (auth, etc0), that anyone can runācomplete with RBAC. It just cascades from there with URLs for runners, monitors, scripts, environments, etc. You have a URL to your entire API lifecycle, across all APIs, across teams.
May we know the roadmap for the Postman desktop version? Does it mean weāre getting a lesser priority in terms of bugs/new features development since the web version is coming?
I would love to see debugging improvements (eg. Having the ability to put breakpoints for Test scripts and not relying solely on console.logs
For a personal perspective, Iād rather install Postman desktop version rather than downloading an 80mb+ that acts as a local server, unless thereās a very persuading reason to migrate to Postman web.
I think having the ability to create a Postman snippet (dynamic link) for simple API requests would be a fantastic feature (JSFiddle-like playground - shareable snippets for those who arenāt using Postman)
May we know the roadmap for the Postman desktop version? Does it mean weāre getting a lesser priority in terms of bugs/new features development since the web version is coming?
Kin Lane - There is no plan to demote or diminish the desktop version. The web, desktop, and API are equal priorities ā here is the road map.
I would love to see debugging improvements (eg. Having the ability to put breakpoints for Test scripts and not relying solely on console.logs
For a personal perspective, Iād rather install Postman desktop version rather than downloading an 80mb+ that acts as a local server, unless thereās a very persuading reason to migrate to Postman web.
Kin Lane - It is our challenge to convince you otherwise. Really it comes down to whether you do API in isolation, or you do APIs in a collaborative way.
I think having the ability to create a Postman snippet (dynamic link) for simple API requests would be a fantastic feature (JSFiddle-like playground - shareable snippets for those who arenāt using Postman)
Ah, I was hoping this would be a solution for me on my Chromebook that doesnāt support Crostini, but unfortunately that doesnāt seem the case, as thereās no way to install the Desktop Agent to work around the CORS issue, right?
I have tried the Postman for the web and here are some ideas (this is just a first look at this new product/idea):
Main ideas:
works almost as good as the Postman App, but there is no compelling reason to switch, not right now
this approach has potential, with so many apps being browser-based nowadays
for most use-cases you still need to install the Postman Agent
does not work from any browser, you are forced to use Windows, macOS, Linux
Ideas on how this can be improved
provide a ācloudā agent to run the requests (privacy issues?, wonāt work for localhost requests)
allow an organization/user to define its own agent IP address (can help with many of the proxy issues that many users experience)
does not work from a phone or a tablet, as you cannot yet install an agent
Honestly, I did not actually understand the part with how the Postman for the web helps with collaboration. I understand that this has potential but many current users may have other priorities right now.
Slightly off-topic, but I have noticed that there might be a disconnect between the Postman roadmap and the more acute pain points that some users have (not saying that the roadmap is not addressing other issues).
Take for example, what @chlkdst mentioned regarding debugging requests. While debugging requests with the console was okay 2-3 years ago, there is no effort or roadmap for addressing this aspect (or I did not notice it).
Can HTTPS request made through Postman Agent?
I installed the server side trust certificate as specified by Chrome, yet Agent returns the following error:
That is Awesome!
This update is great experience for me.
However, I have noticed that i can not use by my iPad browser.
Is this Postman for the web connecting to localhost Postman Agent?
I thought that Postman Agent was tied to my Postman account.
As @vdespa said, It would be great if the Cloud Agent was offered.
We have it disabled for the early beta to reduce challenges with certificates ā just looking to get feedback on core functionality currently, but will be turning on encryption soon.