--- How about this? "eap-" not absolutely necessary prefix for types but I tried to avoid any confusion.
PATCH v2: - dropped phase2 method, new fields types "eap-password" and "eap-response" instead PATCH v1: - dropped challenge, renamed phase2 method RFC: - initial revision doc/agent-api.txt | 27 +++++++++++++++++++++++---- 1 files changed, 23 insertions(+), 4 deletions(-) diff --git a/doc/agent-api.txt b/doc/agent-api.txt index 98499a3..fbae242 100644 --- a/doc/agent-api.txt +++ b/doc/agent-api.txt @@ -61,10 +61,15 @@ Fields string Name Normally returning the "Name" field is the better option here. + string Identity + + Identity (username) for EAP authentication methods. + string Passphrase - The passphrase for a network. For example a WEP - key or a PSK passphrase. + The passphrase for authentication. For example a WEP + key, a PSK passphrase or a password for EAP + authentication methods. string WPS @@ -77,8 +82,9 @@ Fields string Name Arguments string Type - Contains the type of a field. For example "psk", - "wep", "ssid", "wpspin" or plain "string". + Contains the type of a field. For example "psk", "wep" + "eap-password", "eap-response", "ssid", "wpspin" or + plain "string". string Requirement @@ -132,3 +138,16 @@ Examples Requesting a passphrase for WPA2 network } ==> { "WPS" : "123456" } + + Requesting challenge response for a WPA-Enterprise network: + + RequestInput("/service4", + { "Identity" : { "Type" : "string", + "Requirement" : "mandatory" + }, + "Passphrase" : { "Type" : "eap-response", + "Requirement" : "mandatory" + } + } + + ==> { "Identity" : "bob", "Passphrase": "secret456" } -- 1.7.0.4 _______________________________________________ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman