I’m not sure why in 2021 the developers would assume that we only have one login per domain. It’s a strange choice because even casual users have more than one login on many popular sites.
I tried using the built in iOS and macOS password managers and they just aren’t up to the task. I finally switched back to 1Password and I’m very happy I did.
What were the problems that you experienced?
I think that having multiple logins at a given website will work, despite there being only on entry for the website. IIRC, there is an option to use another login when you go to that site. I can’t remember the details but the process wasn’t too onerous.
Anything is possible but I’d make my decision to use keychain or not based on what is available today.
I learned a long time ago to never tell a programmer something is simple. 
YMMV
True. But it is a simple thing compared to everything else that went into the system.
Yes you can, but that’s not the problem. The problem is that there is no way to distinguish between the logins if the username is the same.
My comment was meant to be humorous, but all the programmers I’ve worked with really do resent it when a non-programmer says something is “simple” or “this won’t take very long” etc. Most hide it well, some don’t.
2 Likes
I can see where that would be an issue, but I’m having trouble visualizing a use case where it would occur (I’m probably being dense, it’s one of the things I do best).
My username for shopping at amazon.com is myemail@mydomain.com with password1
My username for Amazon Web Services’ site aws.amazon.com is myemail@mydomain.com with password password2.
An app like 1Password lets me customize the name of these two logins so I can distinguish them. Based on @lukei4655’s post, the macOS passwords feature doesn’t allow this, so when you try to log in both of them look the same.
2 Likes
I’m not on Monterey yet so I haven’t seen the new password feature, but when I was evaluating different password solutions (on Big Sur) I solved this with bookmarks and, as @lukei4655 mentioned, it was tedious, and error-prone as well.
So Monterey passwords isn’t distinguishing between amazon.com and aws.amazon.com?
Funny, I just had a situation at work this week where even I thought the fix of a bug should be simple. But once we discovered the root cause, I see how hard and complex it was to fix it. On the surface things can look simple, but modern computers are so complex under the hood.
2 Likes
Oh I know. Just doubling down on the troll.
1 Like
Well, when I test it I get different things. I just did a sign on to AWS and I was able to follow which login belonged to AWS as opposed to Amazon. But this time the 2FA didn’t activate automatically so I had to go into the Passwords section in Safari to manually copy the code.
So, I don’t know whether there was a glitch when I was testing it the other day, or if there has been a quiet update. But, the last time I was testing this the 2FA automatically tried to populate the correct field, but today it didn’t. So, at this point I’ve become uncertain.
In this screenshot you can see how the two are distinguished. Under the username you see (this website) and the other login shows that it belongs to Amazon. My previous testing, when I first wrote this post, this was not so clearly distinguished. Again, the reason why is unclear.
1 Like
Here is a screenshot of the real problem, that is, 2FA. When I went to sign in to Amazon there was no way to distinguish between Amazon and AWS as you can see for yourselves.
2 Likes
Well, that’s interesting.
I went into keychain and renamed the entries there, but the entries in Passwords didn’t change.
Maybe a security thing.
I haven’t run into any of these problems using Passwords in Monterey. Of course, I’m still early in the process of switching over (I’m doing it site by site instead of importing as csv because of the problem I described). So, there might be more opportunities to find these or other problems.