Hi,
Get Request for Website status Code :200 works with collection, but it does not work with monitor for the same collection and it gives 403. I even do not use any token,authorization or header parameter for the collection.
What can be the reason?
w4dd325
August 12, 2022, 7:52am
2
Hi @descent-module-geol8
Could you maybe screenshot your monitor configuration? |
falquador
August 17, 2022, 11:13am
3
I think it’s due to client certificates not being supported on the Postman Monitoring yet. I had the same issue. You probably have some client-side certificates configured locally on your postman, but those are not taken into account when you use the Postman Monitor.
opened 04:42PM - 31 Oct 17 UTC
feature
product/automation-testing
client-certificates
# Feature Request
We use Postman Pro internally for developing and testing our … APIs. The public endpoints are protected by SSL mutual authentication using client certificates. We would love to be able to set up automated monitoring and testing of our endpoints using Monitors and make full use of our Pro subscription, but currently this doesn't seem to be possible as Monitors don't support the configuration of a client certificate to be used in requests.
Would it be possible to see this on the roadmap for Monitors as it's supported in the clients and newman already?
Dear all,
I have a collection running in the Collection Runner, using HTTPS and a client-side SSL certificate installed in my local postman console (which the administrator of the server has accepted).
I am now trying to run the same collection as a Monitor. I have already applied all suggestions in this link: https://learning.getpostman.com/docs/postman/monitors/troubleshooting-monitors/
The monitor runs, and I can see the request being submitted in the log. Then I receive this error:
Error…
system
December 12, 2024, 12:54pm
4
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
