Provisioning Manager reporting WIFI_PROV_STA_AUTH_ERROR with valid credentitals (IDFGH-10503)

[homedad]

Answers checklist.

• I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
• I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

Does the code below map too many error cases into "Auth Error"?

We have seen this ourselves during development, and now we have several users reporting that they have input their credentials correctly, and the provisioning library reports WIFI_PROV_STA_AUTH_ERROR, with which we tell the user, "Bad Creds". This doesn't help the user solve the problem.

Excerpt from components/wifi_provisioning/src/manager.c (IDF Version 4.4.3):

switch (disconnected->reason) {
        case WIFI_REASON_AUTH_EXPIRE:
        case WIFI_REASON_4WAY_HANDSHAKE_TIMEOUT:
        case WIFI_REASON_AUTH_FAIL:
        case WIFI_REASON_ASSOC_EXPIRE:
        case WIFI_REASON_HANDSHAKE_TIMEOUT:
        case WIFI_REASON_MIC_FAILURE:
            ESP_LOGE(TAG, "STA Auth Error");
            prov_ctx->wifi_disconnect_reason = WIFI_PROV_STA_AUTH_ERROR;

[mahavirj]

@homedad I think you had reported similar issue in #9399, and it was fixed in IDF 4.4.4 release. Can you please confirm if you have that fix available in your code-base? Alternatively, is it possible for you to share the WiFi packet capture for the part when you observe this issue?

[homedad]

Correct. This is a related issue. I will collect data. It’s is rare however in my home environment so this may take some time.

On Fri, Jul 7, 2023 at 5:32 AM Mahavir Jain ***@***.***> wrote: @homedad <https://github.com/homedad> I think you had reported similar issue in #9399 <#9399>, and it was fixed in IDF 4.4.4 release. Can you please confirm if you have that fix available in your code-base? Alternatively, is it possible for you to share the WiFi packet capture for the part when you observe this issue? — Reply to this email directly, view it on GitHub <#11749 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAVP6XBKARUJKQ3DEUN5WRTXO6GPPANCNFSM6AAAAAAZUYYN3U> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- -scott.e