Closed
Bug 920936
Opened 11 years ago
Closed 11 years ago
[User Story] Automatically set default setting to 802.1x EAP-SIM
Categories
(Firefox OS Graveyard :: Wifi, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
1.3 Sprint 6 - 12/6
People
(Reporter: wmathanaraj, Assigned: nhsieh)
References
Details
(Keywords: feature, Whiteboard: [ucid:WLAN2, 1.3:p1, ft:ril])
Attachments
(2 files, 4 obsolete files)
User Story: As a user I expect the default option for WLAN to be 802.1x EAP-SIM authentication if this detected as supported by the hotspot Acceptance Criteria: AC1: as a user I want to see that the default option has been selected as 802.1x EAP-SIM
Flags: in-moztrap?
Updated•11 years ago
|
blocking-b2g: 1.3? → 1.3+
Whiteboard: [FT:RIL, ucid:EAP-SIM2]
Updated•11 years ago
|
Whiteboard: [FT:RIL, ucid:EAP-SIM2] → [FT:RIL, 1.3:p1, ucid:EAP-SIM2]
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → nhsieh
Comment 2•11 years ago
|
||
Hi Neo, I know you are trying to adopt a new design on value selection, I think it's great, but I'm afraid that will cause UI inconsistency in Settings app. As you know, some are using old design with a "OK" button, and some are in your new design with a "Cancel" button. If UX team agrees that it's a better idea, can we file a bug to replace all of them in Settings app (or even the whole system) instead of partially having some in Settings? Besides, re-building another value selector here creates redundant code and is not an effective way to work on.
Flags: needinfo?(nhsieh)
Assignee | ||
Comment 3•11 years ago
|
||
I changed design from one step selector to orignal two step already. Please have a look. If you have any questions, please let me know. Thanks
Flags: needinfo?(nhsieh)
Assignee | ||
Comment 4•11 years ago
|
||
Assignee | ||
Comment 5•11 years ago
|
||
Fixed this bug. -------------------- Hi Neo, in page 8 --> step 2 --> the selector dialog of "Select NSS item" There is still a guiding description("Notice: if you need import CA..) in the bottom side. We are not able to have the description in the system selector. And the "Cancel" button should be "OK". Thanks.
Updated•11 years ago
|
Flags: in-moztrap? → in-moztrap?(hlu)
Target Milestone: --- → 1.3 Sprint 5 - 11/22
Assignee | ||
Comment 6•11 years ago
|
||
Hi all, I upload the new UX specification for fit Gecko engineer's requirement.
Comment 7•11 years ago
|
||
Hi Wilfred, I’ve been told that, Gecko cannot tell if the hotspot is EAP-SIM supported without having successfully connected to it using EAP-SIM authentication. We can (and supposedly need to) set a default method, but currently not able to do the smart detection/setting per hotspot for the 1st time, given the limited information from WiFi scanning. Question1: after first time login to a specific hotspot (bug 920939) using EAP-SIM authentication, device will keep the method setting. Does the behavior cover this story? Question2: what is the expected general default EAP authentication? Methods of v1.3 include PEAP, TLS, TTLS, SIM. From UX document (attachment 829987 [details]), it will be PEAP.
Flags: needinfo?(wmathanaraj)
Updated•11 years ago
|
Whiteboard: [FT:RIL, 1.3:p1, ucid:EAP-SIM2] → [ucid:WLAN2, 1.3:p1, ft:ril]
Reporter | ||
Comment 8•11 years ago
|
||
(In reply to whuang from comment #7) > Hi Wilfred, > > I’ve been told that, Gecko cannot tell if the hotspot is EAP-SIM supported > without having successfully connected to it using EAP-SIM authentication. > > We can (and supposedly need to) set a default method, but currently not able > to do the smart detection/setting per hotspot for the 1st time, given the > limited information from WiFi scanning. > > Question1: after first time login to a specific hotspot (bug 920939) using > EAP-SIM authentication, device will keep the method setting. Does the > behavior cover this story? > This is acceptable for our implementation. We DONT need to select the EAP-SIM method with advanced detection if this is not currently supported in Gecko. > Question2: what is the expected general default EAP authentication? Methods > of v1.3 include PEAP, TLS, TTLS, SIM. From UX document (attachment 829987 [details] > [details]), it will be PEAP. EAP-SIM should be the default configuration
Flags: needinfo?(wmathanaraj)
(In reply to Neo Hsieh from comment #9) > Created attachment 831269 [details] > Settings_WPA_EAP_SIM_131113.pdf > > Change EAP default value from PEAP ro SIM Suppose SIM has to be default in "Join network" page, maybe it has to be mentioned in page 5?
Comment 11•11 years ago
|
||
(In reply to Chuck Lee [:chucklee] from comment #10) > (In reply to Neo Hsieh from comment #9) > > Created attachment 831269 [details] > > Settings_WPA_EAP_SIM_131113.pdf > > > > Change EAP default value from PEAP ro SIM > > Suppose SIM has to be default in "Join network" page, maybe it has to be > mentioned in page 5? Nice catch. Page 5, flow 2, the EAP Method should be SIM.
Comment 12•11 years ago
|
||
Remove blocking-b2g flag from User Story bugs. Use whiteboard to indicate what FxOS version we target.
blocking-b2g: 1.3+ → ---
Comment 13•11 years ago
|
||
Note: As discussion with UX, QA team offline, we have a scenario undefined in spec. page 4, flow 3. After imported CA key from SDCard, there is no CA key in the "Select CA file" list. It will show nothing for guiding user no CA key now.
Updated•11 years ago
|
Attachment #822212 -
Attachment is obsolete: true
Updated•11 years ago
|
Attachment #823797 -
Attachment is obsolete: true
Updated•11 years ago
|
Attachment #823808 -
Attachment is obsolete: true
Updated•11 years ago
|
Attachment #829987 -
Attachment is obsolete: true
Comment 14•11 years ago
|
||
Comment 15•11 years ago
|
||
Add moztrap link: https://moztrap.mozilla.org/manage/cases/?pagenumber=1&pagesize=20&sortfield=created_on&sortdirection=desc&filter-tag=2300
Flags: in-moztrap?(hlu) → in-moztrap+
Updated•11 years ago
|
Target Milestone: 1.3 Sprint 5 - 11/22 → 1.3 Sprint 6 - 12/6
Comment 17•11 years ago
|
||
We fix this user story in Gecko and Gaia. But Vendor need to support EAP SIM function for their platform. Since it depends on what platform is chose by OEM, this part is supposed to be owned by OEM. Using bug 923359 for tracking. But it is not going to block this feature.
Comment 18•11 years ago
|
||
Close this user story. If you want to test this feature, please use a wap_supplicant with enabling EAP-SIM.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•