Feedback and a feature request regarding passkeys on the Mac

Question

Passkeys are still mostly useless on MacOS.&nbsp; Can 1password just bite the bullet already and implement native password manager support on MacOS?&nbsp; Although I love the autofill shortcut (shift+comand+space) and it truly is the best UX I've used on a password manager, that alone isn't enough to make me cough up 1password subscription fees for eternity when it remains fundamentally broken on the OS I'm using all day.
I have a feeling the discussions have gone like this:

Should we implement native password manager support on MacOS?&nbsp; It's yet another platform to support.&nbsp; How many points?
[Estimates]
Hmm, well we've got X that needs to get done this quarter.&nbsp; Next quarter is Y.&nbsp; And we've been putting off Z forever and senior engineers are going to start quitting if we don't fix THAT!&nbsp; Can users live without it?
Well, sure.&nbsp; They've got the browser plugins...
Great!&nbsp; Let's just table this for now and revisit it when we've got more capacity.

Totally understandable!&nbsp; We've all been there.&nbsp; The problem is this really sucks for a few reasons.&nbsp; Here they are:

(MAJOR) Passkeys: Unfortunately on MacOS the browser extensions seem to be the ONLY way to use Passkeys.&nbsp; That is problematic for a few reasons.&nbsp; The biggest issue is that browsers are NOT the only place you might need to auth on a computer.&nbsp; Sure it's 80% or more.&nbsp; But even if it were 99%, the software is not called .99password, it's 1password.&nbsp; I've already run into situations with native apps where I'm being prompted for a passkey.&nbsp; Your current solution will never work here.

You might be thinking:&nbsp; "WHAT!&nbsp; Native apps using passkeys?!&nbsp; That is so rare and uncommon!&nbsp; We cannot expend engineering effort on a mere 1% of use cases!"&nbsp; Sure, maybe now.&nbsp; But it's happened to me multiple times and passkeys are pretty new.&nbsp; I can't imagine they're going away after all the effort to roll them out.&nbsp; It's only a matter of time.
And for people who don't use the browser extensions, they are experiencing this pain every single time they are prompted for a passkey

(GRIPE: Browser extensions) You're almost a victim of your own success (almost).&nbsp; The autofill shortcut works so well I have absolutely no desire to install the much less functional browser extensions.&nbsp; I use several browsers (I'm an engineer) and they honestly are pretty mediocre in how well they work and they're frustrating to use.&nbsp; I should need to log into 1password ONE time.&nbsp; Not 1 + N, where N is the number of browsers.&nbsp; They're constantly prompting me for my password, they need to be kept up to date, and frankly the UX just isn't great.&nbsp; I'm sure for various reasons (like non MacOS operating systems) you need to keep them working, but on MacOS they just aren't the best way to use 1password (nor are they a differentiator - every password manager, free or paid, has these, so I'm certainly not losing anything wrt these by switching away from 1password).

In case you want to interpret this to mean "make browser extensions better", that is NOT what I'm saying.&nbsp; I'm not going to use them.&nbsp; It's simply more unnecessary complexity, more to keep in sync wrt updates, more surface area for attack, etc.&nbsp; Not happening.

Wow.&nbsp; 1password doesn't really support the major authentication initiative that everyone is switching to?&nbsp; Sounds dire!&nbsp; Luckily there is a solution!&nbsp; Unfortunately for 1password, all a user needs to do is stop using 1password. The solution is simple: use the built-in free password manager Apple rolled out recently (alongside the API to actually support passkeys properly, in fact).&nbsp; That works great!&nbsp;
I've simply been saving all my passkeys there.&nbsp; I did have it turned off for a while and was using 1password exclusively.&nbsp; But due to 1password's lack of compatibility with passkeys, it's turned back on.&nbsp; Now whenever it asks to save any of my credentials, I say yes.&nbsp; Eventually, I'm sure it will have pretty much everything.&nbsp; And once it has everything, does it really make sense to keep paying for 1password?
Just implement the dang API already.&nbsp; Get it on the roadmap.&nbsp; A decent engineer could have that production ready in a month if you just said "go" and got out of their way for a while (tell them they don't have to attend any planning meetings if they can meet the deadline, you'll have people fighting to take it).
Sent with ❤️.&nbsp; I never knew a password manager could be so great.&nbsp; If I didn't care and want you to be successful, I wouldn't waste spend my time on this.

tobyx · Answer

I couldn't phrase it any better. The lack of Native macOS Autofill is at best a huge annoyance, at worst completely breaking Passkeys on the system. 1Password already supports this on iOS and iPadOS, and if this is not implemented by the time my subscription runs out, I'm gone. You've had multiple years.

Thanks for the post, it is very much appreciated.

1p_dave · Answer

Hello brandonfryslie​! 👋
Thank you for the feedback! The team is currently focused on supporting 1Password for Safari (the browser extension) and Universal Autofill but I'll make sure to pass along your request to add support for macOS AutoFill in the future. Are you able to tell me which desktop apps you're using that you sign into using a passkey? I can add that to the request that I'll file with the team.&nbsp;
As things stand at the current moment, using 1Password in the browser is the recommended way to save and sign in with passkeys in browsers on the Mac for 1Password. You mentioned:

I should need to log into 1password ONE time.&nbsp; Not 1 + N, where N is the number of browsers.&nbsp; They're constantly prompting me for my password, they need to be kept up to date, and frankly the UX just isn't great.&nbsp;

When you use the browser extensions alongside the desktop app, 1Password should lock and unlock at the same time in every browser that you're using. If you're not seeing that happen then try the steps in this guide: If the 1Password browser extension doesn’t unlock when you unlock the 1Password app
Modern browser will update your browser extensions automatically, is that not happening on your end? You can check to make sure that automatic updates are enabled by following these steps: How to keep 1Password up to date in your browser
You also mentioned the UX, can you tell me a little more about what you find lacking in the UI/UX of 1Password on your Mac? I look forward to hearing from you.
-Dave

1p_dave · Answer

tobyx​&nbsp;
Thank you for the feedback, I can certainly pass your request along to the team as well. Can you tell me a little more about how passkeys are currently broken for you on your Mac? Are you using Safari or another browser?&nbsp;
-Dave

tobyx · Answer

1P_Dave​ — thanks for reaching out!I am using Safari. The behavior is unchanged no matter if I'm using the App Store or Testflight version of the extension. The extension often times will not work at all, making me have to close the whole browser in hopes to revive it again.If it is active and otherwise working, its JS interception of the Passkey flow is flaky. On telekom.com it doesn't work at all, generating an error on the site even when creating the Passkey. Native Autofil paired with Apple Passwords just works fine. On adobe.com I had similar issues, but here it's not the creation, but rather subsequent logins where the extension fails to capture the flow and I'm left with having to login with email and password instead.Just to be clear, when trying to use 1Password, I deactivate all native Autofill behavior on macOS as instructed.Just supporting Native Autofill via Credential Provider Extension API just as you do on iOS and iPadOS would fix the issue.

1p_dave · Answer

tobyx​&nbsp;
Thank you for those details. While I'm not able to create an account to test telekom.com, I do have an existing Adobe account and I was able to sign in using my passkey. I'd like to investigate further why 1Password is failing to sign in, or save, passkeys on your device in certain circumstances and see if you're running into a known issue.
Choosing either telekom.com or Adobe's website, can you reproduce the issue and collect a diagnostics report from 1Password for Safari:Send a diagnostics report (browser extension)Attach the diagnostics to an email message addressed to support@1password.comWith your email please include:

A link to this thread: https://www.1password.community/discussions/1password/feedback-and-a-feature-request-regarding-passkeys-on-the-mac/153360
Your forum username: tobyx
Which website you last reproduced the issue on and whether you were saving a new passkey or signing in using an existing passkey.

You should receive an automated reply from our BitBot assistant with a Support ID number.&nbsp; Please post that number here.&nbsp; Thanks very much!
-Dave

Forum Discussion

Feedback and a feature request regarding passkeys on the Mac

5 Replies

Recent Discussions

Does 1password8 no longer have the watch unlocking feature?

Browser req pw always, instead of using biometric & windows hellow

Browser Extension doesn't autofill 2FA on Mega.nz

Unable to view or create items in non-empty (existing) vault after duplicating to new vault

Request: Turn off username guessing in the apps