Pact Foundation

Team, do we have Pact broker Centos / RHEL based image? Current pact broker image is Alpine based OS image and facing issues with Self-Signed cerificates

What’s the issue and what’s the relationship to RHEL/Centos?

Ok, we have our in-house SSL certificates. How to bake them during runtime?

<https://docs.pact.io/pact_broker/configuration/features#webhook-ssl-certificates>

or rather - what certificate is self-signed?

We are trying to enable webook to trigger an event from Pact broker to our CI system. So while doing that getting the below SSL issue

```ERROR: Error executing webhook OpenSSL::SSL::SSLError - SSL_connect returned=1 errno=0 state=error: certificate verify failed (self signed certificate in certificate chain)```

Please see these instructions on running and accessing a Pact Broker over TLS <https://docs.pact.io/pact_broker/advanced_topics/using-tls/>

yep, the link I provided above should help get you to a point where you can load certificates into PactFlow

Actually, I might need to check how this works with on-prem

I’m following up with a team member, please bare with me - I’ll aim to get back to you on this tomorrow.

If you have the time, you could try to see if <https://github.com/pact-foundation/pact_broker/blob/master/script/prod/insert-self-signed-certificate-from-url.rb> gets you anywhere.

You could of course _disable_ validation to get you by for now (<https://docs.pactflow.io/docs/on-premises/environment-variables#webhooks>). This is obviously not recommended

Coming back. Sorry, I somehow thought this was a PactFlow related question. The article above is correct then.

If you are running PactFlow on-prem, then the script to load it into the DB is the current way to achieve this.

cool, not PactFlow. The docs above should get you going then!

<@U9UUY3CU9>, When we disabled `PACT_BROKER_DISABLE_SSL_VERIFICATION` it is throwing the following puma dependency exception during startup :
```/pact_broker/vendor/bundle/ruby/2.7.0/gems/anyway_config-2.3.0/lib/anyway/type_casting.rb:111: warning: Pattern matching is experimental, and the behavior may change in future versions of Ruby!
/pact_broker/vendor/bundle/ruby/2.7.0/gems/anyway_config-2.3.0/lib/anyway/rbs.rb:40: warning: Pattern matching is experimental, and the behavior may change in future versions of Ruby!
bundler: failed to load command: puma (/pact_broker/vendor/bundle/ruby/2.7.0/bin/puma)```

really? that seems unlikely to do with that change

I would recommend using the latest pact broker image, which is using Ruby 3.2.* as released in May