According the AT command documentation, reading the device certificate is not supported.
That's somehow irritating. There is no reason for that, at least for those who common with certificate based authentication know, that this certificate is send to the server anyway. Therefore I searched the forum for similar issues and found, that this has been already asked
AT%CMNG not showing hashes (and certificates cannot be read so not identified)
At the end of that ticket (November 2021):
"The AT command documentation should have been updated in July 2021, while the support for reading client certificates was added as a feature request in October."
Using a nRF9151 LACA A0A, mfw 2.0.1 I get:
at%cmng=1,44
%CMNG: 44,0,"DA9D07FBC95EE8140D7FE1BBE649B18359AC5CC6EC10A195036212BE4B256A59"
%CMNG: 44,1,"705E99CBF369FA5B773487147DD2BC8AFE898ABB7BD663D542471D70870BB3E3"
%CMNG: 44,2,"2FC319CDEB482BA7E9162390683BB8FD1296AFDC3EAE6C3856718B59B2E2C1EC"
at%cmng=2,44,0
%CMNG: 44,0,"DA9D07FBC95EE8140D7FE1BBE649B18359AC5CC6EC10A195036212BE4B256A59","-----BEGIN CERTIFICATE-----
MIIB6jCCAZCgAwIBAgIIVcDMBTw+KzcwCgYIKoZIzj0EAwIwXDEQMA4GA1UEAxMH
Y2Ytcm9vdDEUMBIGA1UECxMLQ2FsaWZvcm5pdW0xFDASBgNVBAoTC0VjbGlwc2Ug
SW9UMQ8wDQYDVQQHE
at%cmng=2,44,1
ERROR
at%cmng=2,44,2
ERROR
Is it still not possible to read the client certificate? In difference to that statement years ago?
