Result of authenticating using Windows Hello.

State of authenticating using Windows Hello.

Status of biometric authentication availability on Windows.

Status of biometric authentication availability on ChromeOS.

Numeric values correspond to CredentialManagerStatusCodes class.

HTTP credentials were moved during migration to HTTPS HTTP credentials were copied during migration to HTTPS

Triggers that may indirectly cause PasswordStore observers notifications because logins *may* have changed.

Chrome either was notified about external changes (e.g. via subscription notification) or started a new foregrounding session and needs to refresh data that may have changed due to external credential management. A credential was saved by Chrome. Update observers with all credentials because the addition may conflict with an existing credential. A credential was updated by Chrome. Update observers with all credentials because updates may have caused implicit removals (e.g. due to primary key changes) or the update may have failed (e.g. because of a prior deletion). A single credential was removed by Chrome. Update observers with all credentials because removal might fail (i.e. credential was already gone). Multiple credentials where removed by Chrome. Update observers with all credentials because removals might fail. Chrome removed blocklisting entries. Update observers with all credentials to confirm the remaining saving exceptions.

Describes the combination of duplicate credential types found in a password dropdown when it is shown. These are based on credentials sharing the same username. This metric is logged for each distinct type of duplication found in a single dropdown appearance.

A user has multiple password credentials for the same username. A user has multiple passkey credentials for the same username. A user has at least one password and at least one passkey credential for the same username. This is logged even if other duplications (e.g. multiple passwords for this same user) also exist for this user.

Triggers that will cause Chrome to offer to move a password from the profile store to the account store.

The user successfully logged in with a password from the profile store. Recorded only on Win/Mac/Linux. The user explicitly asked to move a password listed in Settings. Recorded on iOS/Win/Mac/Linux. The user explicitly asked to move multiple passwords at once in Settings. Recorded only on Win/Mac/Linux. After saving a password locally, the user opted in to saving this and future passwords in the account. Recorded only on Win/Mac/Linux. The user explicitly asked to move a password to account store from password details page. The user clicked a link in a footer of the manage passwords bubble. For example, it might be because of 3rd party password managers. The password element to be filled has not been found. Filling only happens in iframes if all parent frames PSL-match the security origin of the iframe containing the password field. Passwords are not filled into fields that are not editable. The username field contains a string that does not match the username of any available credential. This typically indicates placeholder values. No credential was filled due to mismatches with the username. This can happen in a number of cases: In case the username field is empty and readonly. In case of a username-first-flow where a user's credentials do contain a username but the form contains only a password field and no username field. In case of change password forms that contain no username field. In case the user name is given on a page but only PSL matched credentials exist for this username. There may be further cases. Renderer was instructed to wait until user has manually picked a credential. This happens for example if the session is an incognito session, the credendial's URL matches the mainframe only via the PSL, the site is on HTTP, or the form has no current password field. PasswordManager.FirstWaitForUsernameReason records the root causes. No fillable elements were found, only possible for the old form parser. User is browsing in incognito mode. A credential exists for a PSL matched site but not for the current security origin. Form is suspected to be a password change form. (Only recorded for old form parser) User is on a site with an insecure main frame origin. User is browsing with the Touch To Fill feature enabled. User is browsing with the Fill On Select feature enabled. Re-authenticaion for filling passwords is required. Password field is already filled in and it doesn't look like a placeholder. A credential exists for an affiliated matched site but not for the current security origin. The form acccepts WebAuthn credentials from an active WebAuthn request. User needs to reauthenticate using biometric. The form is in a cross origin iframe. The only available credential is weakly affiliated. The form is a single username form. An actor task is ongoing on the page. Password change is ongoing on the page.

This enum records the type of a given HTTP credential. Depending on its username and the password, an HTTP credential can have no matching, an equivalent or a conflicting HTTPS credentials. Also the corresponding website can be served with or without HSTS enabled.

A credential exists for a PSL matched site but not for the current security origin. A credential exists for an affiliated android app but not for the current security origin. This is provided as a credential sharing affiliation by AffiliationService. A credential exists for an affiliated site but not for the current security origin. This is provided as a credential sharing affiliation by AffiliationService. A credential exists for another entity, which is grouped with the current domain by the AffiliationService through a grouping affiliation. A credential exists for an android application, which is grouped with the current domain by the AffiliationService through a grouping affiliation. A credential exists for a website, which is grouped with the current domain by the AffiliationService through a grouping affiliation.

The value is a combination of the current sync state and if the user has their sync password saved.

Reason why a provisional save failed.

For example, it might be because of 3rd party password managers.