Feature Request: Support Universal Autofill in apps created using WebCatalog

Thanks for the input ianto I've noted it internally. Nice to talk with you again.

+1 from me for support of the Credential Provider Extension API on macOS (just like you do on iOS and iPadOS).

Main reason for me is the native implementation from Apple is plentifold faster than using the buggy 1Password Extension for Safari.

Please.

Thank you again for the feedback and suggestions, all of your comments have been passed along to our product and development teams. 🙂

-Dave

1P_Dave BTW -- from my perspective Universal Autofill working with ad-hoc signatures was not a "bug" as you call it. It was a killer "feature", that then got removed without proper explanation.

That was the annoyance for me. 😊

Thanks 1P_Dave -- I appreciate the full explanation, and the honesty, and appreciate that you have to prioritise your workload based on customer demand.

I did originally ask for this to be reinstated as an option in settings that you give your customers, with the advice that downgrading Universal Autofill to supporting ad-hoc signatures could potentially compromise security, and then it is our choice rather than yours to take that risk. That would be a simple solution -- but that was not responded to.

I completely agree with @jsorge. With Apple now providing support for browser-based apps I would really really really hope you will support these. 🤞🙏

It might be a more niche feature right now, but when the ability to do this is released with Sonoma demand from your customers will surely increase.

@jsorge

Thank you for the feedback, I've passed along your request to the team. 🙂

-Dave

ref: PB-34131847

I'd like to +1 Ian's request. Having hopped on the Sonoma bandwagon I was hoping these apps made by Safari would be able to work with 1Password's auto-fill (I was really hoping that Safari extensions would come over for free but they don't – so I filed FB12487876 requesting that). It now makes sense why 1Password's app auto-fill doesn't work but I really really really want it to work.

I've used Unite and Fluid in the past with varying levels of success but really yearned for a Safari solution. Now that we have it, not being able to use 1Password is a huge killjoy to using it.

I hope that you all can prioritize supporting new features of macOS and get this built. Thanks!

I'm sorry for the disappointment. For security reasons, Universal Autofill currently requires a valid code signature on all apps that it fills into. WebCatalog apps use "adhoc" code signatures which have no cryptographic proof to back up their validity and are not compatible with Universal AutoFill.

Universal Autofill initially working with apps that use ad-hoc signatures was a bug that was resolved in version 8.7.1 (as you said in your initial post): We now verify the code signature of apps before we allow filling using Universal Autofill.

As mentioned, we do have an internal work item open to investigate supporting ad-hoc signatures without compromising on the security of Universal Autofill but I can't make any promises on when, or if, our development team will be able to build this support. Supporting ad-hoc signatures requires both security and development work and, to be honest, we've received only a limited number of requests to build this support so far.

I know that this isn't the answer that you were hoping for. The request remains filed with the team internally and the team and I will continue to track requests from customers and to advocate to our development team that this is something that some folks find necessary for their workflow.

-Dave

1P_Dave

That internal issue is still in our developer's backlog and I don't have any updates to share at the moment.

That's incredibly disappointing on a number of levels. The initial point I made remains: you released a new feature that was so incredibly helpful, and then pulled it from a later release. A year later still no updates to share.

We don't currently support the Credential Provider Extension API since 1Password already supports filling credentials on macOS using 1Password in the browser and Universal Autofill.

I believe the Credential Provider Extension API is a new feature of macOS Sonoma (?) so I'm not surprised you don't currently support it. My comment was really the hope that you might support it by release of Sonoma later this year, and then 1Password will work with the new Safari web apps when they launch with Sonoma. Please please consider this.

For the time being, have you considered using a Chromium-based browser to create web apps out of websites? If you create a web app using a browser like Chrome then 1Password in the browser is able to fill into that web app.

Yes. I have investigated every option. I won't go into why this is a poor solution for my use case.

@ianjukes

Thank you for following up. The team member that you referred to is on the customer support team, once their initial investigation confirmed the relevant details an internal issue was filed with our development team so that our developers could investigate further. That internal issue is still in our developer's backlog and I don't have any updates to share at the moment. I'm sorry that I'm not able to provide more news.

BUT -- Apple announced at WWDC that Safari 17 will be able to create standalone web apps. I have read that "Web apps work with AutoFill credentials from iCloud Keychain and from third-party apps that have adopted the Credential Provider Extension API."

We don't currently support the Credential Provider Extension API since 1Password already supports filling credentials on macOS using 1Password in the browser and Universal Autofill. I understand that these options don't work for your specific use case and, while I can't make any promises, I've filed a feature request on your behalf to have the team look into supporting the the Credential Provider Extension API in the future.

For the time being, have you considered using a Chromium-based browser to create web apps out of websites? If you create a web app using a browser like Chrome then 1Password in the browser is able to fill into that web app.

-Dave

ref: PB-33771517