Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.38%. Comparing base (3a72f95) to head (73097e2).
⚠️ Report is 37 commits behind head on master.

@@           Coverage Diff           @@
##           master   #17789   +/-   ##
=======================================
  Coverage   98.38%   98.38%           
=======================================
  Files         171      171           
  Lines       22240    22257   +17     
=======================================
+ Hits        21881    21898   +17     
  Misses        359      359           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Code size report:

   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
     mimxrt:    +0 +0.000% TEENSY40
        rp2:    +0 +0.000% RPI_PICO_W
       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS
  qemu rv32:    +0 +0.000% VIRT_RV32

Thanks @UniverCom for submitting this. I took the liberty of making a minor edit in the PR description - the example code block didn't terminate. The description could probably use some more editing in the second half to add some formatting.

A quick look at the changes suggest you've copied an ESP-IDF header (esp_eap_client.h) into the MicroPython repo. That's not something that we would ever accept, you should be able to include the header from the ESP-IDF component.

To be accepted this PR would also need documentation and/or example code, in addition to a proper review.

Have you seen the esp32 WPA Enterprise support submitted in #17234? That PR is more complete and currently under review. It might be a better use of efforts to collaborate on it rather than starting a new approach.

Also, may I ask, did you use an AI coding agent to develop part or all of this PR?

Thanks @UniverCom for submitting this. I took the liberty of making a minor edit in the PR description - the example code block didn't terminate. The description could probably use some more editing in the second half to add some formatting.

A quick look at the changes suggest you've copied an ESP-IDF header (esp_eap_client.h) into the MicroPython repo. That's not something that we would ever accept, you should be able to include the header from the ESP-IDF component.

To be accepted this PR would also need documentation and/or example code, in addition to a proper review.

Have you seen the esp32 WPA Enterprise support submitted in #17234? That PR is more complete and currently under review. It might be a better use of efforts to collaborate on it rather than starting a new approach.

Also, may I ask, did you use an AI coding agent to develop part or all of this PR?

Hi, @projectgus. I am currently a third-year undergraduate student living in my university’s dormitory. Normally, I work in the fields of Machine Learning and Natural Language Processing, developing various projects. About a month ago, I began learning IoT systems in order to advance my design-stage projects. To test my first ESP32 prototypes, I needed to log and monitor sensor data on a local web server, this required connecting the sensors to my university’s Wi-Fi network, since I reside in a campus dormitory.

Upon discovering that MicroPython does not yet support WPA2-Enterprise, I wondered whether I could implement and enable this feature myself. I reviewed the ESP-IDF and C documentation and attempted to integrate the necessary support into my project. Having primarily worked in Python, I lack professional C experience; nonetheless, I read through the documentation, wrote the C code, and consulted AI code agents to identify any gaps or errors. After successfully testing locally and confirming that I could transmit my project’s data to the web server over the dormitory Wi-Fi, I quickly prepared the documentation and opened this pull request.

I have now seen the previous PR you mentioned. My goal in sharing this code here is threefold: to provide a solution for others facing the same issue, to address any remaining shortcomings, and to solicit advice on the best path forward.

I will take your comments into account and revise the PR accordingly. If you have any further recommendations or warnings regarding this submission, I would greatly appreciate your feedback. Alternatively, I am happy to contribute by working through the PR you referenced. Since solving this problem personally has been very rewarding, I endeavored to follow all guidelines when creating this PR but I recognize that my experience in this area may still be lacking. I hope I have not inadvertently caused any complications.

Sincerely Yours.