Closed Bug 1008736 Opened 7 years ago Closed 7 years ago
Fi EAP-TLS UI is confusing and invalid
To my knowledge, EAP-TLS authentication method does not use any login/password tuple and instead rely on a user certificate. The current Settings UI to add a new (hidden) network allows to select WPA-EAP as a security. Once EAP is selected, one can choose the EAP method within: SIM, PEAP, TLS and TTLS. When selecting EAP-TLS, then the UI changes and expects the users to give: - a login - a password - select a server certificate This is just wrong for EAP-TLS, which expects users to enter: - an identity - a user certificate - a CA certificate - a private key - a passphrase Private key and user may be bundled together (PKCS#12 for instance). To my understanding and given how bug 745468 has been renamed, we do not (yet) support EAP-TLS. However, the UI setting is there and it may confuse users in two way: - letting them think EAP-TLS is supported - setting a broken configuration So, if EAP-TLS is not yet supported, we should just not expose it in the settings. If it is, then this UI seems to need to be fixed.
Adding RFC section describing peer certificate validation.
UX specs given in bug 988150 does not mention presenting EAP-TLS method.
Depends on: 988150
We just don't support TLS yet, Gaia will be update after bug 1002314 to show supported EAP methods based on system capabilities.
(In reply to Chuck Lee [:chucklee] from comment #3) > We just don't support TLS yet, Gaia will be update after bug 1002314 to show > supported EAP methods based on system capabilities. I see your linked bug is a gecko one, quite invasive. Why don't you just remove TLS from Gaia for now ? And that does not answers the fact that the current TLS UI is wrong.
I know UI is wrong now, and I like to fix it by Gaia's support for wifi capabilities within this release. Then Gaia team don't have to modify code which will be removed later.
(In reply to Chuck Lee [:chucklee] from comment #5) > I know UI is wrong now, and I like to fix it by Gaia's support for wifi > capabilities within this release. > Then Gaia team don't have to modify code which will be removed later. This code is already landed: people will have to fix it anyway. And it's exposed to users, who will be mislead.
Based on Chuck's comments, I don't think this is a regression, but rather a new feature bug.
UX people, what do you think of this ?
Re-adding Omega for UX comment here. Omega, please comment or just let us know if you agree/disagree with other comments if that's the case.
Ian, is this part of bug 1003054?
Yes, per https://bugzilla.mozilla.org/show_bug.cgi?id=1002314#c8, Gaia have to reach the capability of authentication which are supported in different Gecko version, platform. See "TLS" is not in property "eapMethods" for wifi in 2.0.
Let's dup the two bugs?
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1003054
ni? new UX owner Jenny.
From UX perspective, it's better to remove TLS from the list.
7 years ago
Assignee: nobody → chulee
Comment on attachment 8433987 [details] [review] Pull Request Hi Chuck, Since the bug is duplicated with bug 1003054, the supported options should be referenced from capability API. We have to avoid to change the option on different Gaia version without capability reference. We're afraid that other more options needed to be change again.
It's was my original plan, but bug 1003054 seems won't done within 2.0 time flame. So I think we might need to remove TTL from UI if UX think it should.
(In reply to Chuck Lee [:chucklee] from comment #18) > It's was my original plan, but bug 1003054 seems won't done within 2.0 time > flame. > So I think we might need to remove TTL from UI if UX think it should. Hi Chucklee, I am not sure this patch is needed in 2.0 or not because it is currently in backlog. Let me ni? howie to decide. If yes, you also have to remove the same part in wifi_helper, but to be honest, this feature will be put back soon when you finish the feature, so I think it is not a must-have action at this time especially we are so close to branch out.
Based on the time frame, let's not put in 2.0
Seriously, the fix is a one line until you implement proper feature detection. Let's not ship a broken v2.0, please !
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Attachment #8433987 - Flags: review?(josea.olivera)
Comment on attachment 8433987 [details] [review] Pull Request Sorry guys but I don't feel comfortable enough with reviewing a part of the setting app that I barely know. Forwarding this request to Arthur as he might know. Thanks.
Attachment #8433987 - Flags: review?(josea.olivera) → review?(arthur.chen)
Comment on attachment 8433987 [details] [review] Pull Request Let's hide the menu until TLS is supported.
Attachment #8433987 - Flags: review?(arthur.chen) → review+
Comment on attachment 8433987 [details] [review] Pull Request NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings. [Approval Request Comment] [Bug caused by] (feature/regressing bug #): [User impact] if declined: Users will see options not functioning [Testing completed]: manual test [Risk to taking this patch] (and alternatives if risky): none [String changes made]: none
Attachment #8433987 - Flags: approval-gaia-v2.0?(bbajaj)
Attachment #8433987 - Flags: approval-gaia-v2.0?(bbajaj) → approval-gaia-v2.0+
You need to log in before you can comment on or make changes to this bug.