Each password is synced up between devices for easy access at all times. This also includes other devices that can use Google Chrome, such as iOS devices, Chromebooks, and desktops. Additionally, Google’s Password Manager is ecosystem-wide, meaning you can access the same saved passwords on Google Chrome as well as on your Android device. Users who have used Chrome and Android for a long time will surely rack up hundreds, if not thousands, of different logins, based on my personal experience. There is no limit to how many account credentials you can save in Password Manager. It also saves user names and email addresses associated with an account. In fact, Password Manager does exactly what the name implies – it saves passwords. Google chose a very straightforward, no-frills name for its password-saving service. What does Google’s Password Manager save?

Should I use a third-party password manager instead?.

What does Google’s Password Manager save?.

This implements the mojom::PasswordGenerationAgent interface. The renderer side implementation of password generation. This implements the mojom::PasswordAutofillAgent interface. The renderer side implementation of filling credentials into the DOM and capturing/extracting all relevant information and events from DOM. This implements the mojom::AutofillAgent interface. The renderer side implementation of Autofill, listens to DOM events and autofill UI events, and dispatches them to the password manager specific agents. This is the content specific implementation of the PasswordManagerDriver interfaces.Ī stub for mocking out communication to the renderer in tests. The second one ( password_manager::PasswordManagerDriver) allows the browser to talk to renderers. The first one ( mojom::PasswordManagerDriver) is a mojo interface that allows renderers to talk to the browser. This is actually a collection of two interfaces named *::PasswordManagerDriver. The *::PasswordManagerDriver is the browser-side communication end-point for password related communication between the browser and renderers. It makes the decision which credentials should be filled into a form and whether to offer password saving or updating existing credentials after a successful form submission. It knows about credentials that are stored on disk or a credential typed by the user. This manages the life-cycle of an individual password form.

It is informed about newly observed forms from the renderers and initiates the filling on page load and (together with PasswordFormManager) save/update prompts on form submission. StubPasswordManagerClient stub for mocking out calls to the embedder in tests.Įmbedder agnostic password manager, manages the life-cycle of password forms (represented as PasswordFormManager instances). WebViewPasswordManagerClient //ios/web_view implementation IOSChromePasswordManagerClient iOS implementation This bootstraps the browser side classes at tab creation time. Manages settings (which features are enabled?), UI (popup bubbles, etc.), provides access to the password store, etc.Ĭhrome's implementation of the PasswordManagerClient on non-iOS platforms. PasswordManagerClient interface (1 per tab)Ībstracts operations that depend on the embedder environment (e.g. Here is a summary of the core responsibilities of the classes and interfaces: |AutofillAgent| |PasswordAutofillAgent| |PasswordGenerationAgent| |PasswordFormManagerChromePasswordManagerClient| The ContentPasswordManagerDriver is the content specific implementation of the *::PasswordManagerDriver interfaces.

the ChromePasswordManagerClient is the Chrome-specific implementation of the PasswordManagerClient interface. In reality there exist further abstractions, e.g. For simplicity, it shows the concrete instances in case of Chrome on desktop. The following architecture diagram shows instances of core classes. /chrome/android/java/src/org/chromium/chrome/browser/password_manager/.NOTE: Some embedder specific code must not be part of content (e.g.

Google passwords manager android