Hi,
I've set PublishVerificationResult switch to t...
# pact-netp
Pallavi Anirban Bose
04/07/2023, 8:44 AMHi,
I've set PublishVerificationResult switch to true in my code. Also set up the version
But in pipeline it fails with below error
After adding these switches publish is failing with below error
`publish_verification_results': Error returned from verification results publication 401 (Pact:ProviderVerificationResults:PublicationError)
Am I missing any other setting?
t
Timothy Jones
04/07/2023, 9:32 AM401 means that you’re not authenticated. So you’ll need to check / provide your basic auth username and password for the broker (or access token if you’re using pactflow)
p
Pallavi Anirban Bose
04/07/2023, 10:14 AMThat's already in place while connecting to PactBroker
Pallavi Anirban Bose
04/07/2023, 10:15 AMvar pactUriOptions = new PactUriOptions()
.SetBasicAuthentication(config["PACT_BROKER_USERNAME"], config["PACT_BROKER_USERNAME"]);
pactVerifier
.PactBroker(config["PACT_BROKER_BASEURI"], pactUriOptions);
m
Matt (pactflow.io / pact-js / pact-go)
04/08/2023, 2:10 AM
The error is pretty clear, so I'd be inclined to assume your configuration is wrong (e.g. CONFIG is not populated or the values are incorrect).
Enabling debug logging might help understand further
p
Pallavi Anirban Bose
04/10/2023, 5:12 AMActually @Matt (pactflow.io / pact-js / pact-go)
apparently it seems that issue only. But for us we able to fetch the pact n verify it. Problem only while publishing.
Do we need any other settings as well. Other teams from our org using same creds for publishing. from nodejs / java projects. And it works fine.
From .Net we are receiving this error. So wanted to know if any other setting also required
Pallavi Anirban Bose
04/10/2023, 12:18 PMI've set Verbose = true. my consumer is written using Pact 4x version and Provider is written using 3x, could that be a probable issue with publishing pact verification results? @Matt (pactflow.io / pact-js / pact-go) @Timothy Jones
t
Timothy Jones
04/10/2023, 2:58 PMI would expect that the problem is that the token is not correct or not set
☝️ 1
Timothy Jones
04/10/2023, 2:58 PMthe pact version should not make a difference
✅ 1
Timothy Jones
04/11/2023, 1:16 AMSpecifically:
Copy code
var pactUriOptions = new PactUriOptions()
.SetBasicAuthentication(config["PACT_BROKER_USERNAME"], config["PACT_BROKER_USERNAME"]);☝️ 1
p
Pallavi Anirban Bose
04/11/2023, 5:26 AMok so we need to pass token instead of creds...Thanks a lot. Will try this
Pallavi Anirban Bose
04/11/2023, 5:39 AM@Timothy Jones @Matt (pactflow.io / pact-js / pact-go)
I verified the other applications with in our org, we are using only the user id and password...n it's working fine for tehn w/i any issues.
const publishOpts: VerifierOptions = { pactBrokerUsername: process.env.PACT_BROKER_USERNAME, pactBrokerPassword: process.env.PACT_BROKER_PASSWORD, providerVersion: process.env.GIT_COMMIT || '', providerVersionTags: [process.env.GIT_BRANCH ?? ''], publishVerificationResult: true, pactBrokerUrl: process.env.PACT_BROKER_URL, consumerVersionSelectors: [ { // branch: process.env.GIT_BRANCH, // TODO: proper branch matching latest: true, }, ], };
const opts: VerifierOptions = { pactBrokerUrl: 'https://pact-broker.com', consumerVersionSelectors: [ { latest: true, }, ], ...(process.env.PACT_BROKER_URL && publishOpts),
m
Matt (pactflow.io / pact-js / pact-go)
04/11/2023, 6:06 AM
ok so we need to pass token instead of creds...Thanks a lot. Will try thisthe point Tim was making is that you are passing the username when you should be passing the password
Matt (pactflow.io / pact-js / pact-go)
04/11/2023, 6:07 AM
the token is if you’re using PactFlow or if you’ve added some custom auth. If you have a self-hosted / OSS broker, username/password is what you need
p
Pallavi Anirban Bose
04/11/2023, 6:12 AMI got it...It was very sad mistake from my end. Thanks a lot
😆 1
m
Matt (pactflow.io / pact-js / pact-go)
04/11/2023, 6:14 AM
haha it happens 😉