SAP BN4L-GTT: How to solve Error 407 Client Certificate Failure during TPOF app settings.
I am writing this article to help some SAP Consultants around the world, like me, implementing SAP BN4L-GTT.
Reference: Extractor CreationGuide TPOF document, pages 56 to 58 – Download ABAP Code from GitHub step.
We tried to use New Online option to download code GitHub online repository but the error message below was displayed: Error 407: SSL Handshake with github.com: 443 failed: SSSLERR_CLIENT_CERT_UNTRUSTED (-109) Client certificate verification failed.
We noticed a missing configuration related installation of GitHub.com certificate in our SAP system, through STRUST transaction.
Steps described here in SSL Setup document.
After our Basis Team configured SSL Setup, I did a Connection Test using YABAPGIT_TEST_SSL program, but didn’t work in our first attempt.
Looking again STRUST settings, we noticed that GitHub Certificate was installed in SSL client SSL Client (Anonymous) folder, following SSL Setup document instruction.
Running a new connection test in YABAPGIT_TEST_SSL program, I changed the SSL Identity (P_ID) from “Anonymous” (where a certificate is not used) to “DFAULT” (where a certificate is used).
The connection test was successful this time.
So, I thought that probably YABAPGIT_STANDALONE_NEW program code could be referring to Anonymous SSL settings causing the error.
Our ABAP Developer verified the program code and “Bingo”!
ABAP Code changed to “DFAULT”.
We executed new Online Mode in YABAPGIT_STANDALONE_NEW program again and this time worked.
We were able to use New Online option to download code from GitHub online repository.
Sorry for the long explanation.
I hope this tip help all of you in your SAP BN4L Projects!
Have a nice day!