quatermain
2-way-ssl (Mutual TLS) with HTTPoison and Hackney
Hello,
I have to do requests to some APIs with 2-way-ssl, so every request has to by signed with our cert and private key. We uploaded our certificate to 3rd party servers which provide these APIs.
We put this options into HTTPoison call:
[{:Certificate, cert_der, :not_encrypted}] =
File.read!("/cert/cert.pem") |> :public_key.pem_decode()
key = File.read!("/cert/key.pem") |> :public_key.pem_decode() |> hd |> Tuple.delete_at(2)
[
ssl: [
versions: [:"tlsv1.2"],
verify: :verify_peer,
cacertfile: CAStore.file_path(),
cert: cert_der,
key: key,
depth: 3,
customize_hostname_check: [
match_fun: :public_key.pkix_verify_hostname_match_fun(:https)
]
]
]
When we do request, it looks like server doesn’t know how to process it. Because their api should response error in json format and we got only this:
<html>\n<body>\n<h1>Fault</h1>env:Receiverfault:MessageBlocked</body>\n</html>\n
I tried make request with Postman (NodeJS) with same certificate and private key and it works without problem.
Any ideas where can be problem? I asked on slack and @voltone gave me some good advice but I’m a little bit lost and looks like I did something wrong.
Thanks for any help or suggeston
Marked As Solved
quatermain
So we fixed it. We did this:
changed this:
:hackney.request(method, url, headers, body, req_opts)
to this:
HTTPoison.request(method, url, body, headers, req_opts)
This ssl setup with RSA private key:
[
ssl: [
versions: [:"tlsv1.2"],
verify: :verify_peer,
cacertfile: CAStore.file_path(),
certfile: config(:certificate),
keyfile: config(:private_key),
ciphers: :ssl.cipher_suites(:all, :"tlsv1.2"),
depth: 3,
customize_hostname_check: [
match_fun: :public_key.pkix_verify_hostname_match_fun(:https)
]
]
]
and the most important part in our mix file:
{:hackney, github: "benoitc/hackney", override: true}
Thanks everybody
Also Liked
quatermain
we had to fix it. I didn’t want to change language and it’s for our new product for PSD2 application. Currently we are first in country with license and a lot of customers ask for it for last year. So we have big line of customers waiting for it. Big thanks for community which help us a lot.
voltone
Hmm, so in that case it wouldn’t be an issue of missing intermediates.
The server’s response is not very helpful. If you make a request without client certificate at all, does the server throw a TLS alert, or do you get the same HTML error? I’m trying to understand whether the server is configured to handle mutual TLS auth issues at a higher protocol layer. Most (but not all) servers would reply with a TLS alert. Maybe everything is fine on the TLS layer, and you have a missing HTTP header (“Accept: application/json” ?).
There isn’t anything to try here if you do not have any intermediate CA certificates…
quatermain
HTTP header (“Accept: application/json” ?).
You are the winner. Their API documentation and Sandbox API use for all api calls “application/x-www-form-urlencoded” and their Production API use “application/json” but only for auth api call. Others look like use www-form.
FYI - API owner is group of banks, about 7 countries and 7 banks in EU. So… I will write horror/comedy book after all my NDA will end.
quatermain
I like Mint and Mojito looks very good. But we are not done yet, unfortunately. We have to struggle with custom implementation of Oauth2 for every bank and make it works. We need 10 banks for beginning. Some have same API, just changed endpoint and others have custom implementations. There are about 4 main standards (Berlin Group Standard, Poland Standard, Slovakia standard,…) which we have to implement to cover our regions. We hired new junior and I gave him test project where he has to implement Mint with OpenStreet Map API, so he has to learn messaging and so on. It’s very good for him to use Mint.
ityonemo
Perfect project for a junior!







