MxLoader

 View Only

No credentials were available in the client certificate

  • 1.  No credentials were available in the client certificate

    Posted 09-06-2022 08:49
    Edited by Christopher Winston 09-06-2022 09:24

    Hi!

    When performing a connection test MXLOADER shows the error:
    "No credentials were available in the client certificate".

    Is there a way that I can get MXLOADER to ignore the warning and allow the connection?

    I ask because the certificate issue does not seem to affect Maximo. I have also tested sending the MXLOADER connection test message with Postman (HTTP POST), and while Postman also warns about the certificate, it does not stop the returning response.


    I have also noticed in the Windows Event viewer a message when the connection attempt is made from MXLOADER (or Postman):
    EventID: 36869 - The TLS client credential's certificate does not have a private key information property attached to it.

    This is a self-signed certificate, but I have successfully tested MXLOADER with self-signed certificates in other environments. 
    For this environment, before I installed the certificate locally, the browser would warn the certificate was not secure (but "advanced" allowed me to proceed with the connection anyway).



    After installing the certificate locally in the Trusted Root Certificate Authorities store, the browser no longer complained about the certificate:

     
    Since I am not in control of the certificates and everything else seems to be able to deal with whatever shortcomings the certificate may have, I prefer a solution that does not involve change/re-issue of the certificate. 

    I appreciate any help you can provide.

    Tian



    ------------------------------
    Christian Taljard
    ------------------------------