Hi folks I m experiencing an issue currently when trying to Pact Foundation #pact-jvm

Hi folks. I'm experiencing an issue currently when...

andrewhiles

03/02/2022, 5:05 PM

Hi folks. I'm experiencing an issue currently when trying to publish pacts via gradle. It looks like the request to the broker is dropping auth. If I try and publish to an existing broker that has no auth, it works but when publishing to our new auth’d broker, the request fails. I’m using pact-jvm version 4.2.20 which appears to have fixed some authentication issues but it doesn't appear so in my case. Has anybody else encountered this recently? Any info is appreciated.

andrewhiles

03/02/2022, 5:24 PM

I'm using the standard Gradle

pactPublish

step like most folks

andrewhiles

03/02/2022, 5:24 PM

Copy code

pact {
    publish {
        pactDirectory = "$rootDir/pacts"
        pactBrokerUrl = "<https://url/sub-path/>"
        pactBrokerUsername = "xxx"
        pactBrokerPassword = "xxx"
    }
}

andrewhiles

03/02/2022, 5:26 PM

On inspecting the request it looks like the auth headers are dropped, resulting in a generic error -

<http://au.com|au.com>.dius.pact.core.pactbroker.InvalidNavigationRequest: Failed to fetch the root HAL document

uglyog

03/03/2022, 12:16 AM

Pact-JVM publishes some Pact files to an authenticated broker as part of it's release build, so it definitely works. There must be something else that is the problem.

Matt (pactflow.io / pact-js / pact-go)

03/03/2022, 6:03 AM

Can you please share any logs Andrew? Might need to set the log level to debug so we can see the req/res from the broker

Matt (pactflow.io / pact-js / pact-go)

03/03/2022, 6:05 AM

It looks like you are running the pact broker on a context path - it’s possible that has been misconfigured. What happens is Pact JVM -> request to broker at the root (

/sub-path

in your case). It then sends back a HAL JSON response with links to follow. If the broker doesn’t know it’s running on that path, those links won’t have the prefix and will result in badness

Matt (pactflow.io / pact-js / pact-go)

03/03/2022, 6:05 AM

andrewhiles

03/14/2022, 6:36 PM

Apologies for the delayed response on this one - Unfortunately I am still encountering this issue

andrewhiles

03/14/2022, 6:37 PM

We did encounter several subpath issues that were resolved in the most recent version of the OSS Pact Broker instance - I don't believe the subpath is causing issues here, though

andrewhiles

03/14/2022, 6:39 PM

We're using

pact-jvm

with

gradle

to build pacts and publish them..from the debugging I've performed, it looks like no matter we try, the

pactBrokerUsername

and

pactBrokerPassword

values are not being sent in the request to the broker

andrewhiles

03/14/2022, 6:39 PM

The errors I am seeing are similar to an issue raised in the #C9VPNUJR2 channel by David Van Couvering on Tues 8th March

andrewhiles

03/14/2022, 6:40 PM

I've checked network logs and these requests do not have a basic auth'd user attached..however, if I try and publish pacts using a

pact-node

codebase or using the

pact-cli

directly - I can publish pacts with no issue

andrewhiles

03/14/2022, 7:05 PM

I've tried multiple ways to get this working with Gradle and passing in system variables, etc - no option seems to persist the auth in the requests

andrewhiles

03/15/2022, 4:15 PM

@Matt (pactflow.io / pact-js / pact-go) @uglyog - any ideas?

Matt (pactflow.io / pact-js / pact-go)

03/16/2022, 12:00 AM

Sorry I’m not sure, I don’t know JVM/Pact JVM well enough to advise. Usually, verbose/debug logging will get you there though

Open in Slack

Previous Next