You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/connectivity/networking/api/wifi.rst
+18-17Lines changed: 18 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,42 +97,43 @@ To facilitate installation of the certificates, a helper script is provided, see
97
97
The script will install the certificates in the ``rsa2k`` directory to the TLS credentials store in the device over UART and using TLS credentials shell commands.
98
98
99
99
100
-
To initiate Wi-Fi connection using enterprise security, use one of the following commands depending on the EAP method:
100
+
To initiate a Wi-Fi connection using enterprise security, use one of the following commands depending on the EAP method:
Server certificate is also provided in the same directory for testing purposes.
121
121
Any AAA server can be used for testing purposes, for example, ``FreeRADIUS`` or ``hostapd``.
122
122
123
123
Certificate requirements for EAP methods
124
124
----------------------------------------
125
125
126
-
Different EAP methods require different certificates on the client side:
126
+
Different EAP methods have varying client-side certificate requirements, as outlined below:
127
127
128
-
* **EAP-TLS**:
129
-
Requires both a client certificate (and private key) and the CA certificate on the client. The client authenticates itself to the server using its certificate.
128
+
* EAP-TLS - Requires both a client certificate (and its private key) and a CA certificate on the client.
129
+
The client authenticates itself to the server using its certificate.
130
130
131
-
* **EAP-TTLS-MSCHAPV2**:
132
-
Requires only the CA certificate on the client. The client authenticates to the server using a username and password (MSCHAPV2) inside the TLS tunnel. No client certificate is needed.
131
+
* EAP-TTLS-MSCHAPV2 - Requires only the CA certificate on the client.
132
+
The client authenticates to the server using a username and password <MSCHAPV2> inside the TLS tunnel.
133
+
No client certificate is needed.
133
134
134
-
* **EAP-PEAP-MSCHAPV2**:
135
-
Requires only the CA certificate on the client. Like TTLS, the client uses a username and password (MSCHAPV2) inside the TLS tunnel and does not need a client certificate.
135
+
* EAP-PEAP-MSCHAPV2 - Requires only the CA certificate on the client.
136
+
Like TTLS, the client uses a username and password <MSCHAPV2> inside the TLS tunnel and does not require a client certificate.
0 commit comments