Hey folks, in our company we are self-hosting the Pact-Broker and want to put it behind a Cloudflare Zerotrust tunnel and disable the Pact-Broker's own basic auth. This means that we have to send custom headers for authorization (

CF-Access-Client-Id

and

CF-Access-Client-Secret

with the calls to the Pact-Broker. In our pipeline we are using the Pact CLI tool which is only sending basic auth token as far as we understood. Same goes for Pact JVM for our unit tests which are communicating with the Pact-Broker. Do you have any idea how one could solve this issue or is there a feature planned to be able to send custom headers as well?

Makes sense. There are no plans I’m aware of, but might be worth searching the relevant GitHub repos to see if there are any feature requests already. I don’t see why we wouldn’t allow such a support. This is the relevant repo: https://github.com/pact-foundation/pact_broker-client (assuming no changes needed to comms to the broker as it terminates at the gateway?)

Thanks for your reply, Matt. I see that there is a request on the Pact Broker Client but no reply yet: Support for Custom Headers (e.g., CF-Access-Client-Id/Secret) in Pact CLI · Issue #185 · pact-foundation/pact_broker-client Same for the Pact JVM, where someone was able to modify the @PactBroker annotation to make it work: https://github.com/pact-foundation/pact-jvm/issues/1835 I was hoping that these changes might be in progress already. As long as that is not the case I have to see if we are able and have the time to customize them