TLS handshake error using mbedTLS

I'm implementing an OAUTH procedure on my device.  I'm able to access login.microsoftonline.com and get user and device codes, then after authorizing, I can access the token endpoint and get an access token.  I'm using the root ca DigiCert Global Root CA.

But then when I got to the customer's server (which is an azure instance) I try to connect and I get a TLS handshake error;

TLS handshake error: -2700

I have no idea of what that error is or how to go about debugging is.  I'm using the same root ca as I use for login.microsoftonline.com and since it's azure, I'm assuming that is OK.

Any thoughts, or cipher suites I should try to enable.  Anything that I can try since I'm kind of stuck right now.

Thanks

Parents
  • The error in the SSL/TLS handshake actually establishes a secure connection between the web server and the client (such as a web browser). It is called the SSL Handshake 525 Failed. It can happen for multiple reasons, sometimes due to an issue at the client’s end and sometimes from the server’s end. There are many reasons the handshake fails from both the client side and the server side.

    1) Incorrect Date and Time settings

    2) Invalid SSL/TLS Certificate

    3) Incorrect Cipher Suite Selection

    4) Interference with the SSL handshake by firewalls or proxies

    5) Network connectivity

    6) Server Configuration Issues

    Many different ways to fix the error are also available there, which can help understand the solution.

Reply
  • The error in the SSL/TLS handshake actually establishes a secure connection between the web server and the client (such as a web browser). It is called the SSL Handshake 525 Failed. It can happen for multiple reasons, sometimes due to an issue at the client’s end and sometimes from the server’s end. There are many reasons the handshake fails from both the client side and the server side.

    1) Incorrect Date and Time settings

    2) Invalid SSL/TLS Certificate

    3) Incorrect Cipher Suite Selection

    4) Interference with the SSL handshake by firewalls or proxies

    5) Network connectivity

    6) Server Configuration Issues

    Many different ways to fix the error are also available there, which can help understand the solution.

Children
No Data
Related