Closed Bug 922930 Opened 7 years ago Closed 6 years ago

[User Story] WPA EAP: To support PEAP and TTLS for EAP.


(Firefox OS Graveyard :: Wifi, defect)

Gonk (Firefox OS)
Not set


(feature-b2g:2.0, tracking-b2g:backlog)

2.0 S3 (6june)
feature-b2g 2.0
tracking-b2g backlog


(Reporter: kchang, Unassigned)



(Keywords: feature, Whiteboard: [ucid:WLAN6, 2.0, ft:RIL])


(1 file)

We need to support other WPA-Enterprise methods. Here are the items.
1. To support PEAP, TLS, and TTLS for EAP.
2. To support PAP, MSCHAP, MSCHAPV2 for phase 2.
Blocks: b2g-WLAN-1.3
Depends on: 917102, 917175, 917176, 790056
Depends on: 926341
Summary: [User Story] To support PEAP, TLS, and TTLS for EAP. → [User Story] WPA EAP: To support PEAP, TLS, and TTLS for EAP.
blocking-b2g: --- → 1.3?
Whiteboard: [ucid:, 1.3:p2, ft:ril]
blocking-b2g: 1.3? → 1.3+
Remove blocking-b2g flag from User Story bugs. Use whiteboard to indicate what FxOS version we target.
blocking-b2g: 1.3+ → ---
Target Milestone: --- → 1.3 Sprint 5 - 11/22
Target Milestone: 1.3 Sprint 5 - 11/22 → 1.3 Sprint 6 - 12/6
Actually the story covers WLAN6, 7, 8, 9, 10, 11, 12, 13
Whiteboard: [ucid:, 1.3:p2, ft:ril] → [ucid:WLAN6, 1.3:p2, ft:ril]
Depends on: 926334
Update whiteboard tag to follow format [ucid:{id}, {release}:p{1,2}, ft:{team-id}]
Whiteboard: [ucid:WLAN6, 1.3:p2, ft:ril] → [ucid:WLAN6, 1.3:p2, ft:RIL]
blocking-b2g: --- → madai?
Whiteboard: [ucid:WLAN6, 1.3:p2, ft:RIL] → [ucid:WLAN6, 1.4:p1, ft:RIL]
Target Milestone: 1.3 Sprint 6 - 12/6 → ---
1.4 user story supposedly needs to be complete before Sprint3.
Will communicate with team to reconfirm target milestone.
blocking-b2g: madai? → backlog
Whiteboard: [ucid:WLAN6, 1.4:p1, ft:RIL] → [ucid:WLAN6, 1.4, ft:RIL]
Target Milestone: --- → 1.4 S3 (14mar)
Flags: in-moztrap?(hlu)
I flashed images-keon-v1.3-2014-01-24.Gecko-8baca69.Gaia-0a79a06 yesterday.

With 1.1 and 1.2 my Geeksphone Keon could connect with PEAP to a company provided wireless network (which uses WPA2-EAP). It went away with 1.3 where only SIM is offered as EAP Method. It also announces the network as WPA-EAP. Or is this something different?
WPA-EAP PEAP/TLS/etc modes are temporarily disabled until we can support server certificate, see bug 789217 comment 2, and we are working to support that in 1.4.
Move it out from 1.4 feature.
Blocks: backlog-RIL/Net/Conn
No longer blocks: b2g-WLAN-2.0
Target Milestone: 1.4 S3 (14mar) → ---
Whiteboard: [ucid:WLAN6, 1.4, ft:RIL] → [ucid:WLAN6, ft:RIL]
Blocks: b2g-WLAN-2.0
No longer blocks: backlog-RIL/Net/Conn
After discussing with EPM, UX, Gaia dev, and QA, we will support PEAP and TTLS for 2.0.
And we only plan to support MSCHAPV2 for phase 2 method.
Summary: [User Story] WPA EAP: To support PEAP, TLS, and TTLS for EAP. → [User Story] WPA EAP: To support PEAP and TTLS for EAP.
No longer depends on: 998223
No longer depends on: 998226
Whiteboard: [ucid:WLAN6, ft:RIL] → [ucid:WLAN6, 2.0, ft:RIL]
Please see Bug 988150 for the latest UX spec.
Flags: in-moztrap?(hlu) → in-moztrap?(echang)
feature-b2g: --- → 2.0
Test cases
search for tag named "bug 922930"
Flags: in-moztrap?(echang) → in-moztrap+
QA Contact: echang
Target Milestone: --- → 2.0 S3 (6june)
resolve fix this bug as all dependent bugs are fixed.
Closed: 6 years ago
Resolution: --- → FIXED
For tracking purposes - 
A user is reporting this issue in the SUMO forums with a ZTE Open C device (v1.3):

My understanding from the latest comment in this bug is that this feature has been implemented and will land on version 2.0, is this correct?

Thanks in advance! =)
- Ralph
Flags: needinfo?(hochang)
It's already landed now, but recently we found that it will malfunction on devices using base image from android 4.3 or later, see bug 1020212.
Yes Ralph! Also see Comment 16 for known issue, thanks.
Flags: needinfo?(hochang)
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.