[PR #1512] [MERGED] WPA2 Enterprise PEAP support #1770

New issue

Closed

opened 2026-02-28 02:12:56 +03:00 by kerem · 0 comments

kerem commented

2026-02-28 02:12:56 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/tzapu/WiFiManager/pull/1512
Author: @jameshi16
Created: 10/16/2022
Status: ✅ Merged
Merged: 10/19/2022
Merged by: @tablatronix

Base: PEAP ← Head: master

📝 Commits (3)

a1223df Added preliminary WPA2_Enterprise PEAP support
c402fc0 Remove unncessary printf
654e673 Delete enterprise config after connecting to normal AP

📊 Changes

3 files changed (+147 additions, -10 deletions)

View changed files

📝 WiFiManager.cpp (+136 -7)
📝 WiFiManager.h (+4 -0)
📝 strings_en.h (+7 -3)

📄 Description

Hi,

I'm currently working in an environment where I have to connect the ESP32 to a WPA2 Enterprise network protected with PEAP. Given the nature of such a network, the credentials are used for more than just WiFi. I was hence uncomfortable with configuring my username & password directly on a sketch that I would be sharing, so I decided to use WiFiManager.

The PR contains some code to get WiFiManager working with PEAP-protected networks. Is implementing support for WPA2 Enterprise networks currently on the roadmap?

I had to use my own NVS storage, as it seems like the ESP32 framework doesn't automatically save credentials for anything outside of a typical SSID & Password combo.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/tzapu/WiFiManager/pull/1512 **Author:** [@jameshi16](https://github.com/jameshi16) **Created:** 10/16/2022 **Status:** ✅ Merged **Merged:** 10/19/2022 **Merged by:** [@tablatronix](https://github.com/tablatronix) **Base:** `PEAP` ← **Head:** `master` --- ### 📝 Commits (3) - [`a1223df`](https://github.com/tzapu/WiFiManager/commit/a1223dfd6d94768fb15e1aa74a911837b48fd0e8) Added preliminary WPA2_Enterprise PEAP support - [`c402fc0`](https://github.com/tzapu/WiFiManager/commit/c402fc01b34de6e0299a3fb7a2447e643a74c1b8) Remove unncessary printf - [`654e673`](https://github.com/tzapu/WiFiManager/commit/654e673b12acae83c58be29abf8a81c5a496f614) Delete enterprise config after connecting to normal AP ### 📊 Changes **3 files changed** (+147 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `WiFiManager.cpp` (+136 -7) 📝 `WiFiManager.h` (+4 -0) 📝 `strings_en.h` (+7 -3) </details> ### 📄 Description Hi, I'm currently working in an environment where I have to connect the ESP32 to a WPA2 Enterprise network protected with PEAP. Given the nature of such a network, the credentials are used for more than just WiFi. I was hence uncomfortable with configuring my username & password directly on a sketch that I would be sharing, so I decided to use WiFiManager. The PR contains some code to get WiFiManager working with PEAP-protected networks. Is implementing support for WPA2 Enterprise networks currently on the roadmap? I had to use my own NVS storage, as it seems like the ESP32 framework doesn't automatically save credentials for anything outside of a typical SSID & Password combo. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>