CC3200 Secure Sockets - Client Certificates

I suspect you have either got the incorrect certificate or the desktop app is having issues. You need to first make sure the certificate you have works with your application. 

Regarding whether you have the right format, can you view the certificate when it is on the harddrive, it should look like a certificate. 

Glenn

Aashish,

Thank you, but those files do not provide an explanation of using client certificates to authenticate with a server. I have been able to connec to the server using the Server's CA file. I have also been able to connect to the server using the client certificates that I have flashed to the CC3200 while on a desktop connection, and the server verifies them. My original post had an error in that I receive the error code

"#define SL_ESECBADPRIVATEFILE                 (-458)  /* error secure level bad private file */"

Not the one listed above.

A code snippit below of how I am setting up the socket:

#define SL_CA_FILE "/cert/129.der"
    retVal = sl_SetSockOpt(n->my_socket, SL_SOL_SOCKET,
                                                 SL_SO_SECURE_FILES_CA_FILE_NAME,
                                                 SL_CA_FILE,
                                                 strlen(SL_CA_FILE));
    if (retVal < 0) {
        return retVal;
    }

#define SL_CERT "/cert/130.der"
    retVal = sl_SetSockOpt(n->my_socket, SL_SOL_SOCKET,
                                                 SL_SO_SECURE_FILES_CERTIFICATE_FILE_NAME,
                                                 SL_CERT,
                                                 strlen(SL_CERT));
    if (retVal < 0) {
        return retVal;
    }
#define SL_KEY "/cert/131.key"
    retVal = sl_SetSockOpt(n->my_socket, SL_SOL_SOCKET,
                                                 SL_SO_SECURE_FILES_PRIVATE_KEY_FILE_NAME,
                                                 SL_KEY,
                                                 strlen(SL_KEY));
    if (retVal < 0) {
        return retVal;
    }

Thanks to all for your help.

Resolved it. Thanks for help TI. It was a format error. The key hadn't converted formats.

Hi,

I am having the same difficulties with connecting via TLS and receive the same error code.

I do not really understand how I can convert my private .key into .der. I can find a lot of documentation how to use openssl and other tools to convert a certificate to .der, but I cannot find anything for .key to .der conversion at all... Can anybody give me some guidance how I can perform this conversion?

Cheers,

Fabian

Hello Fabian,

This post has been closed long ago.

For better tracking, is it possible that you open a new thread and reference to this one for reference?

I can answer on the new thread.

Regards,

Shlomi