Automatically detect & store OAuth login method (Google/GitHub/Apple/etc.)

Hi everyone,

I’d like to suggest a feature that would solve a very common problem for users who sign in to websites using OAuth providers (e.g., Sign in with Google, GitHub, Apple, etc.).

Right now, Bitwarden can save traditional username/password logins, but it does not automatically detect or store which OAuth provider was used for a given site. After some time (months or years), it’s easy to forget which provider was used to sign in, and accidentally logging in with a different provider can create a second unwanted account — or expose an email we don’t want to share.

The problem

  • Many sites offer multiple OAuth login options.

  • Bitwarden does not capture this information.

  • After a long time, users often forget whether they originally logged in with Google, GitHub, Apple, Facebook, etc.

  • Manual notes or custom fields can be added, but this defeats the convenience and purpose of a password manager, and relies on the user always remembering to do it manually.

Proposed solution

Bitwarden could:

  1. Automatically detect when a login flow uses OAuth (e.g., Google/GitHub/Apple redirect URLs, OAuth endpoints, or JavaScript SDK triggers).

  2. Store the chosen provider in the saved login item (e.g., as a tag, a custom field, or a provider indicator).

  3. Optionally display a reminder when returning to the site:
    “You previously signed in using: Google”

  4. Allow users to manually adjust or override the detected provider if needed.

Why this matters

  • Avoid creating duplicate accounts by mistake.

  • Improve convenience for users who regularly use OAuth.

  • Reduce confusion when logging in after long periods.

  • Makes Bitwarden more helpful for modern authentication patterns, where passwords aren’t always used.

This would be a highly useful quality-of-life improvement, and many modern sites rely heavily on OAuth for authentication. Having Bitwarden track the provider would make the login experience much smoother.

Thanks for considering this!

2 Likes

A post was merged into an existing topic: Social / third-party login