Back in #42 I added the option for a custom http client. I missed a few areas leading to a situation where there are 2 differently configured http clients used right now.
This lead to a funny issue where the initial connection to a keycloak using a custom CA was working fine but all subsequent connection attempts failed because it used the default reqwest::Client instead...
Back in #42 I added the option for a custom http client. I missed a few areas leading to a situation where there are 2 differently configured http clients used right now. This lead to a funny issue where the initial connection to a keycloak using a custom CA was working fine but all subsequent connection attempts failed because it used the default reqwest::Client instead...
I hope I found all spots this time.