Closed
Bug 705767
Opened 13 years ago
Closed 13 years ago
Validate credentials before completing setup
Categories
(Firefox for Android Graveyard :: Android Sync, defect, P1)
Tracking
(firefox16 verified, blocking-fennec1.0 -)
VERIFIED
FIXED
mozilla16
People
(Reporter: rnewman, Assigned: liuche)
References
()
Details
(Whiteboard: [sync][qa!])
Attachments
(1 file)
41.25 KB,
patch
|
Details | Diff | Splinter Review |
Filing here until we get a component.
Reporter | ||
Updated•13 years ago
|
Component: General → Android Sync
QA Contact: general → android-sync
Summary: Native Sync: validate credentials before completing setup → Validate credentials before completing setup
Reporter | ||
Comment 2•13 years ago
|
||
I expect most setup processes to be via J-PAKE, so this isn't an immediate concern.
OS: All → Android
Updated•13 years ago
|
tracking-fennec: --- → ?
Updated•13 years ago
|
tracking-fennec: ? → 11+
Comment 4•13 years ago
|
||
Is this implying the state of "Connect" button also? Meaning that it should be disabled if, for example the email address is not in a valid email address format, or if the sync key has less characters than a valid sync key, or one of the fields is not empty.
Assignee | ||
Comment 5•13 years ago
|
||
In the current m-c build, the connect button should not be enabled if any of the fields is empty - please reopen bug 711868 with the device you are using if this is the case (if relevant).
This does bug does not include validation checks for email and sync-key size (AFAIK actually, XUL fennec sync did not validate email addresses).
Reporter | ||
Comment 6•13 years ago
|
||
This bug is about "live" validation -- that is, before you complete setup, make some network request and do some work to make sure that the credentials you've entered will be able to sync. That's a superset of syntactic validation.
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → liuche
Reporter | ||
Updated•13 years ago
|
Priority: -- → P2
Updated•13 years ago
|
Keywords: fennecnative-releaseblocker
Updated•13 years ago
|
blocking-fennec1.0: --- → +
Updated•13 years ago
|
Status: NEW → ASSIGNED
Updated•13 years ago
|
Whiteboard: [sync]
Assignee | ||
Comment 8•13 years ago
|
||
Pull request in github awaiting review and feedback.
Comment 9•13 years ago
|
||
re-nomming as this should be a beta blocker or not a blocker at all, and closing the related string bug, as l10n says no strings without features.
blocking-fennec1.0: + → ?
Updated•13 years ago
|
blocking-fennec1.0: ? → -
Assignee | ||
Comment 10•13 years ago
|
||
Github pull request:
https://github.com/mozilla-services/android-sync/pull/143
Not blocking Fennec, so won't be landing anytime soon.
Reporter | ||
Updated•13 years ago
|
Hardware: All → ARM
Whiteboard: [sync] → [sync][patch waiting]
![]() |
||
Updated•13 years ago
|
Whiteboard: [sync][patch waiting] → [sync][patch waiting][qa^]
Updated•13 years ago
|
Whiteboard: [sync][patch waiting][qa^] → [sync][please land on nightly][qa^]
Reporter | ||
Comment 11•13 years ago
|
||
Needs a fix. Back to Chenxia.
Whiteboard: [sync][please land on nightly][qa^] → [sync][qa^]
Assignee | ||
Comment 12•13 years ago
|
||
depends loosely on patch from bug 717707.
Attachment #630323 -
Flags: feedback?
Assignee | ||
Comment 13•13 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/9e508c1d3d6d
STR:
- Launch Sync setup. Click "Advanced Setup" to launch manual credential entry.
- Type in credentials.
- Manually sleep the device (or wait for powersave).
Expected:
Username and Sync Key are not cleared; password field will be cleared.
Assignee | ||
Comment 14•13 years ago
|
||
Whoops, wrong bug STR and inbound link.
https://hg.mozilla.org/integration/mozilla-inbound/rev/5685dcf1f147
STR:
1. Launch Sync setup, click on "Advanced Setup" to go to manual credential entry.
2. Enter username, password, sync key.
3. When all three fields are non-empty, "Connect" should become clickable.
4. If either username or password is incorrect, verification should fail.
Notes:
- Please test w/ non-email-form usernames as well (from early sync accounts), because these should also work.
Comment 15•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla16
Reporter | ||
Comment 16•13 years ago
|
||
Comment on attachment 630323 [details] [diff] [review]
Validate credentials patch
Not a blocker, and code already landed. Clearing flag.
Attachment #630323 -
Flags: feedback?
Comment 17•13 years ago
|
||
verified with latest nightly
Status: RESOLVED → VERIFIED
Whiteboard: [sync][qa^] → [sync][qa!]
Comment 19•13 years ago
|
||
This was minused blocking fennec1.0 back in April. Lingering tracking 11+ flag has caused some confusion. So I am removing that flag and marking status-firefox16 verified as that was the eventual target milestone. Then was fixed and verified in m-c at that time.
tracking-fennec: 11+ → ---
status-firefox16:
--- → verified
Updated•12 years ago
|
Product: Mozilla Services → Android Background Services
Updated•7 years ago
|
Product: Android Background Services → Firefox for Android
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•