403 Error On Monitor While It works Well With Collection

falquador · August 17, 2022, 11:13am

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.

github.com/postmanlabs/postman-app-support

Feature Request: Client certificate support for Monitors

opened 04:42PM - 31 Oct 17 UTC

powelli

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?

Topic		Replies	Views
How to set and check client-side SSL certificate in monitor? Help Hub monitors	1	5168	January 28, 2020
Monitors fail (https certicate aren't used?) Help Hub monitor	1	1034	January 16, 2020
Problem with Monitors not working Help Hub monitors , automation , collections , oauth2	9	2283	June 26, 2023
Monitoring Authorization Error Help Hub	2	2074	January 4, 2021
Monitor calls failing Help Hub monitors , collections	1	53	October 2, 2024

403 Error On Monitor While It works Well With Collection

Related topics