Skip to content

wifi: enterprise: Pull support for runtime certificates #21228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 3, 2025
Merged

wifi: enterprise: Pull support for runtime certificates #21228

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 1 addition & 45 deletions doc/nrf/app_dev/device_guides/nrf70/wifi_advanced_security_modes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,52 +18,8 @@ The nRF70 Series devices support the following Wi-Fi enterprise security mode, `
This mode uses the Extensible Authentication Protocol (EAP) with Transport Layer Security (TLS) for authentication.
The client and the authentication server exchange certificates to authenticate each other.

See `Zephyr Wi-Fi management`_ for more information on how to configure and use the Wi-Fi enterprise security mode.

Enterprise testing: X.509 certificate headers generation
========================================================

Wi-Fi enterprise security requires use of X.509 certificates.
Test certificates in PEM format are available at :zephyr_file:`samples/net/wifi/test_certs/` repository.
During the build process, the certificates are converted to a C header file that is included in the Wi-Fi shell module or the :ref:`Wi-Fi credentials <lib_wifi_credentials>` library.

To use custom certificates, use the following commands:

.. code-block:: bash

$ cp client.pem samples/net/wifi/test_certs/
$ cp client-key.pem samples/net/wifi/test_certs/
$ cp ca.pem samples/net/wifi/test_certs/
$ cp client.pem samples/net/wifi/test_certs/client2.pem
$ cp client-key.pem samples/net/wifi/test_certs/client-key2.pem
$ cp ca.pem samples/net/wifi/test_certs/ca2.pem

$ west build -p -b <board> samples/net/wifi -- -DEXTRA_CONF_FILE=overlay-enterprise.conf

.. note::
The EAP phase2 certificates (suffixed with 2) are unused in ``WPA2-EAP-TLS`` but are mandatory for building the sample application.
The phase1 certificates are copied as phase2 certificates to avoid build errors as a temporary workaround.

To establish a Wi-Fi connection, use the following command:

.. code-block:: console

uart:~$ wifi connect -s <SSID> -k 7 -a anon -K <key passphrase>

.. code-block:: console

uart:~$ wifi_cred add -s <SSID> -k 7 -a anon -K <key passphrase>


.. note::

The Wi-Fi credentials only support 16characters for the anonymous identity and the key passphrase.

The server certificate is also provided in the same directory for testing purposes.
You can use any AAA server for testing purposes, such as FreeRADIUS or hostapd.

.. note::

The certificates are for testing purposes only and should not be used for production.

.. _ug_nrf70_developing_wifi_psa_support:

Expand Down