Open
Bug 2081826
Opened 1 month ago
Updated 27 days ago
[meta] Require profile authentication for sensitive data on Android Automotive OS
Categories
(Firefox for Android :: Autofill, task)
Tracking
()
NEW
People
(Reporter: joberhauser, Unassigned)
References
(Depends on 4 open bugs)
Details
(Keywords: meta, Whiteboard: [fxdroid][android-activation-trust])
For the Android Automotive OS (AAOS) MVP, password and credit card autofill, password management, and password and credit card sync were disabled (bug 2060659, bug 2060936) instead of requiring profile authentication.
This meta bug tracks the profile authentication work that will let us turn those features back on. All of it sits behind a Nimbus feature that is off by default, so the work can land while the features stay disabled.
Once the feature is enabled on AAOS:
- If profile authentication (device lock pattern, PIN, or password) is not set up, show an AAOS-specific setup prompt every time the user tries to:
- manage passwords or credit cards
- autofill passwords or credit cards
- sign in to their Mozilla account
- The prompt offers "Cancel" instead of "Later". Cancelling blocks the action.
- If profile authentication is set up, the user must authenticate before any of those actions.
- Saving a new password or credit card does not require authentication.
- Address autofill does not require authentication.
- The check runs every time. If the user removes their device lock later, the setup prompt shows again.
Updated•1 month ago
|
Comment 1•27 days ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox for Android::Autofill' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Component: General → Autofill
You need to log in
before you can comment on or make changes to this bug.
Description
•