Gotcha. I think I can help with this.
In the doc http://docs.exosite.com/tutorials/provisioning/ there is openssl command:
openssl req -x509 -nodes -days 365 -sha256 -subj /C=US/ST=MN/L=Mpls/O=Exosite/CN=00000002 -newkey rsa:2048 -keyout adc-key.pem -out adc-cert.pem
I was able to read through a couple docs I found on the UC20 here:
Are you using the
FILE AT (referenced in SSL_AT_Commands_Manual chapter 5.1) command to load
adc-cert.pem onto the UC20? Can you share the results of the following command to verify the cert:?
openssl x509 -in adc-cert.pem -text -noout
In the SSL_AT_Commands_Manual I saw in chapter 5.1 there are some troubleshooting tips. Also, it looks like the UC20 does some level of cert verification so I would double check a couple of potential gotchas:
- Are the system clocks on the computer creating the key/cert pair and the UC20 in sync? The cert has a timespan of validity (e.g. if the computer creating the cert/key thinks it’s today but the UC20 thinks it’s 1970 then it won’t work). This is covered in chapter 1.4 of the SSL_AT_Commands_Manual.
- Verify the cert/key pair that you’re loading onto the UC20 has the correct file encoding. Some modules don’t know how to decode unicode, for instance. ASCII/ANSI is likely a safe bet.
You can verify basic parameters of the cert with
openssl x509 -in certificate.crt -text -noout
Let me know if this helps.