Other Parts Discussed in Thread: CC3120
CC3120 Boost Rev A can't Connect via TLS 1.2. Authentication Failed for Enterprise network.----Any Suggestions
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
CC3120 Boost Rev A can't Connect via TLS 1.2. Authentication Failed for Enterprise network.----Any Suggestions
I have updated latest Service pack sp_3.16.0.1_2.0.0.0_2.2.0.7.bin on my CC3120.
Still it is communicating through TLS1.0 only. When I change TLS settings support as only TLS1.2 in Radius server it failed.
Is there any way to initiate Enterprise connection through TLS1.2 using CC3120?
Which TI WIFI module supports Enterprise connection through TLS1.2? Without TLS1.2 will this support 4096 bit certificate?
The transceiver solutions (WL18xx) can be updated to support TLS1.2 (since the supplicant and TLS stack are on the Linux host).
Unfortunately, the existing WL18xx SDK doesn't support this.
Can you please confirm CC3120 Wifi Module supports Enterprise certificates with SHA-384 and RSA 4096?
I will need to check this.
The TLS stack (with a service pack) will support this (for TLS over TCP), but i'm not sure if anything needs to be changed in the supplicant to enable this.
I'll update when i find the info.
Hi Aria, I have tested in my RADIUS and have seen that after the service pack upgrade to : sp_3.16.0.1_2.0.0.0_2.2.0.7, infact did support a 4096 RSA, SHA-384 certificate. I also have a similar issue with trying to get this chip to authenticate via TLS 1.2. The data sheet says it supports it so, I am a bit confused what we are doing wrong here.
Hi Galen,
thanks for the confirmation.
The datasheet (saying TLS1.2 is supported) refers to the TLS stack in general as it is used by the networking apps.
The RADIUS connection requires updating the supplicant which was not done. This limitation for the enterprise was not mentioned in the datasheet by mistake. The document should be updated soon to mentions this specific limitation.