shill: WiFi: Provide wpa_supplicant a PIN if asked for
There are conditions under which wpa_supplicant will clear the
"pin" property of its configuration, even if this was previously
supplied by shill. Under these circumstances it wil request it
again as the EAP negotiation starts. This change provides the
means for the WiFi object to detect when this parameter is being
requested and to supply this value to wpa_supplicant if the
WiFiService has this information on hand.
BUG=chromium:310296
TEST=Unit tests + new autotest:
https://chromium-review.googlesource.com/174170
This autotest still fails the following but shows in the supplicant logs:
CTRL_IFACE: response handle field=PIN
EAPOL: received control response (user input) notification - retrying pending EAP Request
indicating that the PIN has been successfully provided to wpa_supplicant
Change-Id: I91bc3ddd01a335f93d20cca4d47ca497bd631ebe
Reviewed-on: https://chromium-review.googlesource.com/174180
Reviewed-by: mukesh agrawal <quiche@chromium.org>
Commit-Queue: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
diff --git a/wpa_supplicant.h b/wpa_supplicant.h
index 466f5bd..9736bc0 100644
--- a/wpa_supplicant.h
+++ b/wpa_supplicant.h
@@ -38,6 +38,7 @@
static const char kEAPParameterAlertUnknownCA[];
static const char kEAPParameterFailure[];
static const char kEAPParameterSuccess[];
+ static const char kEAPRequestedParameterPIN[];
static const char kEAPStatusAcceptProposedMethod[];
static const char kEAPStatusCompletion[];
static const char kEAPStatusLocalTLSAlert[];