Error when having '&' in pact broker username

[DavidRadianu1]

When using the verifier.verify_with_broker method, with a broker usermame containing &, I get the following error:
'4o' is not recognized as an internal or external command,. 4o is the rest of the broker username after the '&' character.

[mefellows]

Have you tried URL encoding the value?

[DavidRadianu1]

I get the following error after URL encoding:
Error making request - OpenSSL::SSL::SSLError SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed , attempt 1 of 3

[mefellows]

Cool. So now you need to put a real certificate on your broker instead of one of those cheap and nasty enterprise ones ;)

You can specify the cert file via environment variables (see https://docs.pact.io/pact_broker/advanced_topics/using-tls#connecting-to-a-pact-broker-running-over-tls).

[DavidRadianu1]

I tried to do it in Javascript with the same username and password and it worked fine with '&' in the username

[DavidRadianu1]

Is there no way to fix this in python, without using the tls? I can not use that method as I work at a company which utilizes the username + password to connect to the broker

[mefellows]

I tried to do it in Javascript with the same username and password and it worked fine with '&' in the username

It might be that the JS library URL escapes the values, whereas this package seems like it doesn't. I think that's worth investigating (i.e. potential bug).

Is there no way to fix this in python, without using the tls? I can not use that method as I work at a company which utilizes the username + password to connect to the broker

If your broker is running on TLS I'm not sure how you could connect to it from Python without it? Username/password (basic auth) is separate to TLS altogether. You need to be able to tell the python runtime about the self-signed certificate, because by default it's not trusted. Disabling that trust is probably not what you want