Closed Bug 1631130 Opened 5 years ago Closed 5 years ago

Record in telemetry when a login is recorded as used

Categories

(Toolkit :: Password Manager, task, P1)

task

Tracking

()

RESOLVED FIXED
mozilla78
Tracking Status
firefox-esr68 --- wontfix
firefox75 --- wontfix
firefox76 --- wontfix
firefox77 - wontfix
firefox78 --- fixed

People

(Reporter: MattN, Assigned: MattN)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Whiteboard: [passwords:telemetry])

Attachments

(2 files)

We have big blind spot in password manager usage as we don't know when users are using a saved login other than via about:logins (copy/reveal) and autofill on page load (which doesn't mean the user actually submitted the form). We currently only know when a login is autofilled, saved or updated. Bug 1621520 will record filling via the context menu and autocomplete but that doesn't necessarily mean the saved login was submitted afterwards.

We do have PWMGR_LOGIN_LAST_USED_DAYS but it includes all logins put into buckets so can't easily tell you whether the user used any saved logins in a session.

Flags: qe-verify+

Ideally we would exclude manually typing the saved login values and know which UI/UIs was/were used to fill the login but we can probably add that to extra_keys later… for now we can include a boolean indicating whether any fill happened (using autoFilledLoginGuid) but it won't take any user edits after the fill into account.

It would also be nice to include whether the login was breached/vulnerable to align with bug 1622693.

(In reply to Matthew N. [:MattN] (PM me if request are blocking you) from comment #1)

It would also be nice to include whether the login was breached/vulnerable to align with bug 1622693.

Both of these are kinda expensive to compute for every login used so I think I will leave this out for now.

Assignee: nobody → MattN+bmo
Status: NEW → ASSIGNED
Depends on: 1633040

Also fix some incorrect/outdated histogram metadata.

A patch is up but I am still working on tests.

We'll want this telemetry as part of bug 1617759 separate from bug 1628849 to measure when login forms are submitted to see if import suggestion results in more submissions.

Blocks: 1617759
See Also: → 1628849
Depends on: 1640096

[Tracking Requested - why for this release]: See comment 5.

It would be great if this could be reviewed ASAP so we can uplift this to 77. Sorry for the last minute request.

Attachment #9150999 - Flags: data-review?(chutten)

(In reply to Matthew N. [:MattN] (PM me if request are blocking you) from comment #6)

[Tracking Requested - why for this release]: See comment 5.

Is this essential for 77? I've been busy and didn't realize the last beta was today. Not sure if this would be taken for RC, it does seem low risk.

Flags: needinfo?(edilee)

Su says this is nice to have for the password import suggestion experiment and the main experiment goals are still fine with the telemetry that has already landed/uplifted to 77. So no need to rush this in.

Flags: needinfo?(edilee)
Comment on attachment 9150999 [details] Request for data collection review form DATA COLLECTION REVIEW RESPONSE: Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate? Yes. This collection is Telemetry so is documented in its definitions file [Events.yaml](https://hg.mozilla.org/mozilla-central/file/tip/toolkit/components/telemetry/Events.yaml) and the [Probe Dictionary](https://telemetry.mozilla.org/probe-dictionary/). Is there a control mechanism that allows the user to turn the data collection on and off? Yes. This collection is Telemetry so can be controlled through Firefox's Preferences. If the request is for permanent data collection, is there someone who will monitor the data over time? Yes, :MattN is responsible. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under? Category 2, Interaction. Is the data collection request for default-on or default-off? Default on for all channels. Does the instrumentation include the addition of any new identifiers? No. Is the data collection covered by the existing Firefox privacy notice? Yes. Does there need to be a check-in in the future to determine whether to renew the data? No. This collection is permanent. --- Result: datareview+
Attachment #9150999 - Flags: data-review?(chutten) → data-review+
Pushed by mozilla@noorenberghe.ca: https://hg.mozilla.org/integration/autoland/rev/c13f1b0f78ad Record in telemetry when a login is recorded as used. r=sfoster
Depends on: 1640311
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla78

Hey Matt, we should see "pwmgr" "saved_login_used" when an autofilled login was submitted, right? Is this telemetry recorded once per session, per site? When you have the time, please fill in the important details to verify so we can check it out on Nightly.

Flags: needinfo?(MattN+bmo)

(In reply to Timea Cernea [:tbabos] from comment #13)

Hey Matt, we should see "pwmgr" "saved_login_used" when an autofilled login was submitted, right?

Yes, all uses where what was submitted matches a password (and sometimes username) that was saved for the site.

Is this telemetry recorded once per session, per site?

No, it's each use.

When you have the time, please fill in the important details to verify so we can check it out on Nightly.

There are a few follow-up dependencies already filed to take into account and I will write tests in bug 1640311. For now just do a basic check that any time a password is used via a form or an auth. dialog that the event is shown.

Flags: needinfo?(MattN+bmo)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: