question about CONFIG_NRF_CLOUD_PROVISION_CERTIFICATES

[MosheSmartAmr]

Hi, 

If I understand corrctly, the flag CONFIG_NRF_CLOUD_PROVISION_CERTIFICATES=y should only be used once,

after that, the certificates are saved inside the modem.

when I disable this flag, the nordic would not connect due to certificate issue.

any thoughts? 

[MosheSmartAmr]

Further explaining what I see, 
after activating this flag I can read the certificates with the `AT%CMNG=1` command.

after re-flashing without the flag, I cannot see those certificates.

meaning, the certificate storage is not persistent.

[jbrzozoski]

That doesn't match with my experience.  I was using my own application, but I had directly copied the NRF_CLOUD_PROVISION_CERTIFICATES code block as my starting point.  I ran the nrf_inbuilt_key_write provision code once.  Now, on power up, even after re-flashing my application, calling nrf_inbuilt_key_exists confirms there is still a  certificate there.

I also can connect to a server based on "openssl s_server" with the "-Verify" option and confirm it is still using the same client certificate.

Persistence nominally does work for me.  Unfortunately there may be quite a few differences between the NRF_CLOUD library and how my application does things, so I'm not sure what in particular is causing your issue.

[MosheSmartAmr]

anyone else has this issue?