ObliviOS Developer portal Project site

Home / Decisions / ADR-202

Amend ADR-190 (2) (owner instruction 2026-10-29, after the vault asked to save the phone's own screen-lock password and said it would save a login it already held…

Accepted, recorded 29 October 2026.

Decision
ADR-202
Date
2026-10-29
Status
AcceptedAccepted (the owner's instruction; vendor/freeholdos/passwords 989f78b and 80d4ae8)
Mentions
ADR-185, ADR-190
Mentioned by
ADR-190

1Decision

Amend ADR-190 (2) (owner instruction 2026-10-29, after the vault asked to save the phone's own screen-lock password and said it would save a login it already held: "that makes the password manager extremely worthless"): the Passwords app offers to save a login only (1) for a site believed from a trusted browser or for an app that is no part of the system image (an app of the system image gets neither fill nor save), (2) in an app only when the form has a username field, and (3) never when the domain index says that the vault already has an account for the site or app, locked or open.

The clause of ADR-190 that the offer appears on every login form so that it tells nothing about which sites have an account no longer holds.

2Why and evidence

[verified-in-source] PasswordsAutofillService.onFillRequest attaches SaveInfo only when offersSave(fields, webDomain, hasAccount) holds, OriginPolicy.resolve gives a system app Origin.None; [verified-in-source] the autofill framework shows no save for values that a dataset filled and the user did not change. Host: FillTest 166, OriginTest 31, 14 mutants of the new rules killed (PWM-023).

3Consequences

The vault never asks for what it holds or for what is not a login of the user.

4Review when

The absence of the offer on a site now tells whoever uses the phone that an account exists, which the entry that asks for authentication already told (ADR-185 (3)), and an app cannot see it. A changed password or a second account of a known site is not offered: the user edits the entry in the app. A system app with a legitimate login (none known) gets nothing; flip OriginPolicy.resolve. The check of the account is by the domain index, so a login of a linked package that the index does not know is offered.

Read from docs/governance/decision-log.md, entry ADR-202.