https_client connection results in error 22 if build with option EXTRA_CONF_FILE=overlay-tfm-nrf91.conf

[Jason]

Hi all,

I'm working with my custom nRF9151 board and i'm testing https request with option that use native TLS for my download client. 

I got connect err = 22, so i come back to sdk and try to test example https_client with my nRF9151DK.

1. If i build with cmd: west build -b nrf9151dk_nrf9151_ns, i can connect successfully with modifying the cert.

2. If i build with cmd: west build -b nrf9151dk_nrf9151_ns -- -DEXTRA_CONF_FILE="overlay-tfm-nrf91.conf" , i can't connect successfully, even with the cert in case 1.

The error log is:

Connecting to example.com:443
connect() failed, err: 22

[Håkon Alseth]

Hi,

 

There was a certificate change on the default domain used, where the newest one in NCS v3.0.0 is required:

https://github.com/nrfconnect/sdk-nrf/tree/main/samples/net/https_client/cert

 

In addition, the new certificate uses a different crypto algorithm, so the latest configurations in overlay-tfm-nrf91.conf is required:

https://github.com/nrfconnect/sdk-nrf/blob/main/samples/net/https_client/overlay-tfm-nrf91.conf

 

Using ncs v3.0.0, with overlay-tfm-nrf91.conf included in the build, I get this output:

*** Booting nRF Connect SDK v3.0.0-3bfc46578e42 ***
*** Using Zephyr OS v4.0.99-a0e545cb437a ***
HTTPS client sample started
Bringing network interface up
Provisioning certificate
Connecting to the network
+CGEV: EXCE STATUS 0
+CEREG: 2,"8169","014ACE00",7
%MDMEV: PRACH CE-LEVEL 0
+CSCON: 1
+CGEV: ME PDN ACT 0
%MDMEV: SEARCH STATUS 2
+CEREG: 1,"8169","014ACE00",7,,,"11100000","11100000"
Network connectivity established and IP address assigned
Looking up example.com
+CGEV: IPV6 0
Resolved 23.215.0.136 (AF_INET)
Connecting to example.com:443
Sent 61 bytes
Received 318 bytes

>        HTTP/1.1 200 OK

Finished, closing socket.
+CEREG: 0
+CGEV: ME DETACH
+CSCON: 0
Network connectivity lost
Disconnected from the network

  

Could you the above suggestions?

 

Kind regards,

Håkon