Register as macOS Password Provider

Feature Requests Password Manager
, ,
1

Similar to iOS, macOS provides system settings to allow third-party apps to register as password AutoFill sources. This is particularly relevant for the “Set up codes in…” and “AutoFill passwords and passkeys” sections in System Settings.

While Bitwarden handles this role perfectly on iOS, it doesn’t currently appear to be an option on macOS (as of macOS 26.2 and BW client 2026.1.0 (55383). As services increasingly steer users toward passkeys, being able to register Bitwarden as the system provider would greatly help avoid “split” vaults where passkeys inadvertently end up in Apple’s “Passwords” app instead of Bitwarden.

I don’t mean to trivialize the effort or testing required to implement this, but I did some digging into the Apple AuthenticationServices requirements. It seems to hinge on a few key items for the macOS Desktop client:

  • Extension Subclass: Implementing ASCredentialProviderViewController to handle system-level credential requests.

  • Entitlement: Adding the com.apple.developer.authentication-services.autofill-credential-provider entitlement to the app bundle.

  • Info.plist Flag: Explicitly declaring TOTP support by adding the ProvidesOneTimeCodes key (set to true) within the ASCredentialProviderExtensionCapabilities dictionary. Without this flag, macOS doesn’t recognize the app as a “code generator” candidate for the dropdown menu.

  • Onboarding: Leveraging ASSettingsHelper to help users jump directly to the correct toggle in System Settings.

I believe this integration would make the macOS experience feel just as native and seamless as it is on mobile.

5 Likes
2

I second this. I am running into issues where I can’t auto-fill passwords or passkeys on apps or pwas because Bitwarden cannot be registered as a passkey provider. Please add this functionality.

3

FWIW, A similar feature request has made it to the roadmap.

4

I support this request. Native MacOS integration would be far superior to an auto type feature.

5

I fully support this.

6

In which case, you might consider scrolling to the very top of the Feature Request and click “Vote”.

7

Thank you for the reply but this website will not allow me to vote. It says ‘lock’. Apparently I don’t have enough time on here to be allowed to vote.

8

The solution for that is to spend about 15 minutes browsing the community and reading a bunch of topics. Then you will be gifted with 20 votes.

2 Likes
9

Adding another voice in support for this, given it’s implemented for iOS I’d love to see it on macOS as well. I’ve recently been trying to move to passkeys for more services, and this not working is a bit of friction, especially when the Passwords app then takes over. Would love to see this implemented!

10

Note: I removed “passkeys” from the title, since a) there already is a feature request about that (Desktop app - native use of passkeys (macOS, Windows)) and b) “native use of passkeys for MacOS” is on the roadmap.

11

… and somehow, I think Bitwarden might already consider implementing “auto-type” for MacOS as a “native” integration (for passwords – and native passkey support)…

Those feature flags (thanks to @grb for the link) mention “native credential sync” for MacOS – and only for Windows it is called “autotype”:

/* Autofill */
  ...
  MacOsNativeCredentialSync = "macos-native-credential-sync",
  WindowsDesktopAutotype = "windows-desktop-autotype",
  WindowsDesktopAutotypeGA = "windows-desktop-autotype-ga",
  ...

But of course only my personal speculation…