Currently, managing Client Certificates in tools like Postman involves manually saving and referencing .crt and .key files stored locally. This process is inefficient for APIs using frequently regenerated certificates, making automation challenging for test suites that depend on dynamically generated certs. Apidog could improve this by allowing .crt and .key values to be stored as environment variables, enabling seamless usage of these variables as valid certificates. This would eliminate the need for manually creating and referencing physical files, streamlining workflows and supporting automated test suite execution where certificates are generated, used, and discarded dynamically.
Additionally, enhancing the client certificate configuration UI by enabling multiple certificates to be assigned to the same domain, with a radio button to select the active one, would improve flexibility for users managing multiple certificates. These features would greatly enhance Apidog’s usability for certificate-based authentication workflows, setting it apart as a modern and automation-friendly testing tool.
This limitation has been a highly requested improvement in Postman, as seen in: Ability to use Client Certs Programmatically · Issue #4753 · postmanlabs/postman-app-support · GitHub