What’s great about creating a custom field in 1Password is that you can just tap that field to copy and paste into the data entry field on your browser or app. With a note in the passwords app, that requires selecting the text in the note and then long-pressing to copy before you paste.
BitWarden had a similar problem for me - there was no way to create a custom field to store those extra bits of authentication, such as answers to security questions, without using the notes field.
Lastly, because Apple passwords is synced with iCloud Keychain, if Apple, say, deletes your account, with 1p (or another manager) you won’t lose your password manager as well.
These last two are, admittedly, not all that much of a risk.
Maybe not as unlikely as I would like after reading this article.
I use Apple Passwords for simple logins and actually logging in, and 1Password as a secure reference for a lot of other stuff (including the logins which are also in Apple Passwords).
From an abundance of caution I also export 1Password to a CSV database (kept in encrypted DMG) every month or two.
Well, remember that even if your iCloud account is closed, you’d be able to at least export your passwords to a file from a Mac which you could then import to another password manager. (You can export as well from an iPhone or iPad, but only to another app, so you’d have to plan ahead to have the new app installed before you lost access to the App Store.)
Thanks for everyone’s comments. I think I’ll do the following:
Clean up all my logins in 1Password. Get rid of accounts I no longer use.
Export my passwords to Apple Passwords.
Keep my 1Password as my backup.
I’ll use Apple Passwords as my main password manager, but try to keep 1Passwords in sync with that. This way, if I’m away from an Apple device, I can use 1Passwords, and if my Apple account is deleted, I still have 1Passwords.
One of the issues I have is Apple Passwords and 1Passwords colliding when I go to a website to create a new account, both offer password suggestions and cover up some of the webpage
Well, remember that even if your iCloud account is closed, you’d be able to at least export your passwords to a file from a Mac which you could then import to another password manager
Thanks, but surprised that it’s is possible to export passwords without access to my iCloud account.
I made the switch from 1Password to Apple Passwords 1.5 years ago under macOS Sonoma and associated iOS. I did the CSV export routine that worked reasonably well to get passwords into Apple Passwords, including the 2FA information. I had forgotten how many software licenses I had stored in 1Password, so I am glad that I kept access to the CSV file for a while. Passwords for Windows has gotten better. I did have a group sharing problem, but it is no different than Apple Messages not syncing occasionally. One does the logout/login drill and things work again. The less tech savvy people in my family switched to Passwords and are happy with it. Good luck in your switch over.
Apple passwords are stored on the local device, not on iCloud - iCloud Keychain is used for syncing, not for the app’s storage. So if the iCloud account is closed, you can still access your passwords stored on the device. A Mac will still be usable even if the iCloud account is closed.
I’m in the same boat now with Minimalist shutting down. An answer engine not approved for mention here on Tidbits suggested Secrets by Outer Corner as a “stronger” choice than Uplock though I may initially check out using Apple Notes for non-Passwords compatible data.
This is the path I took about 2 years ago. Cleaning up 1PW passwords was cathartic. I rid myself of redundant accounts, and created many new logins to eliminate duplicate passwords. It took a long time, but made me feel better for the exercise.
From memory, importing went reasonably well and I started using Passwords straightaway. I’ve had no real issues and as others have said, I can store all sorts of notes, questions, account details etc within the note section of Passwords.
I stopped paying for 1Password at V7. It still opens, and I can access data, but receives no updates. In the time since switching to Passwords, I’d say I’ve opened 1PW two or three times, and that was to extract old work passwords which I didn’t move to Passwords (because I’d retired). I’ll keep it on my current machine but see little reason to migrate it when a new machine comes along.
I took a look at Secrets. It doesn’t seem to get updated often, reviews on Mac App Store are pretty mixed with several 1 star reviews. The ability to use extended Markdown to make a text entry in the notes field hidden and to make an entry in monospaced font to more easily see numbers is neat, but I’ll stick with Access/Uplock.
For those of use with years of forswearing the devil and all his Microsoft product minions, Passwords is probably as good as or better than 1Password. If you have a device with facial or fingerprint recognition, Passwords is certainly more convenient to use (for me, at least). The most objectionable ‘feature” of 1Password today is that it stores your account information and passwords in an AWS database. Apple is not perfect is these regards, but its cloud uptime and security (especially) appear to be considerably better than Amazon’s.
AWS’s problems are very much a function of the application using it.
Regarding availability, AWS has multiple geographic regions. You can deploy an app across multiple regions in a way that will let one keep operating when another goes down. But that’s an expensive deployment, so not everybody chooses to deploy this way.
Similarly about security. I have read countless news reports about data breaches resulting from an S3 storage pool having no actual security. No authentication, no passwords, no SSH keys. Just obscurity, assuming (very wrongly) that nobody would guess the magic URLs needed to access the data.
But Amazon provides a very robust set of security tools for AWS, including ones where even Amazon can’t access your data (e.g. encrypting via client apps using a private key that’s not stored in the cloud). The facilities for strong security exist, but an application developer has to choose to use (and pay for) them.
What is 1PW doing to secure their AWS databases? I don’t know. But I wouldn’t assume that there are going to be security problems just because it’s AWS. Just like I wouldn’t assume that something stored on iCloud has to be secure. No matter what cloud service you select, ultimate responsibility for security always lies with the app developer.
100%. Even though I should know better by now, I continue to be shocked when I ask a vendor to provide some documentation about how they secure their cloud apps, and they provide nothing more than Amazon’s documentation about Amazon security practices. Sometimes, they act offended when I tell them that their app security is not the same thing as Amazon platform security. I take that as a red flag and have ended contract negotiations or due diligence analyses in my day job as a result.
Just want to add that Apple currently is an AWS customer (and Google Cloud and possibly, I’d say, MSFT Azure). So hosting may not be a major point of differentiation between Passwords and 1Password…but if I had to bet, Apple probably is committing more resources per user to its security on AWS. Maybe I’ll do some digging on that when I get some time.
It might not be the most popular opinion, but “diversification” is NOT a consideration for me. Quite the opposite. I have to trust Apple’s cloud, and I want to absolutely minimize the number of different cloud services I engage with. That’s hard these days. For me, when 1Password went ‘cloud’, that was an immediate deal breaker.
I do miss the ability of 1Password to store data other than passwords. I’d like to put credit card details into a ‘password safe’, but couldn’t figure out how to do it in Apple Passwords.app (without creating some synthetic bogus URL.)