Apple password not working via Safari

ChrisR

I'm a well known grump...
Messages
11,233
Name
Chris
Edit My Images
Yes
Trying to login to my Apple ID via Safari, I had all sorts of trouble, even changed my password, but it still wouldn't work, even immediately afterwards. It has my email address saved correctly, but when I enter the password (copied from the password manager), I just get that annoying little sideways dance. However, when I try the same process with Firefox, it works fine!

Any ideas?
 
I always save password for this site when the dialogue window pops up and never had a problem. Can I ask why you are copying and pasting from password manager, I have never had to do this. when I go to a site that I have registered and log in the password field is automatically filled in for me.
 
I always save password for this site when the dialogue window pops up and never had a problem. Can I ask why you are copying and pasting from password manager, I have never had to do this. when I go to a site that I have registered and log in the password field is automatically filled in for me.
I guess it was a long time since I'd last logged in, but ISTR it did auto-fill the password (presumably from the Keychain) and that wasn't accepted. I then went to the password manager to check it, tried typing it by hand, same result. Then I changed it (which was complicated and bizarre and eventually involved my phone), so I put the new password in the password manager.
It isn't adding a space on the end when you copy and paste is it?
No, I don't think any space was added. I used the same process for both Safari and Firefox, but also hand typed the password for both.

I am on Sonoma 14.7, Safari Version 18.0 (19619.1.26.111.10, 19619) (whatever all that means).
 
Someone on the Apple Community (I logged in via Firefox) wondered whether my software was up to date, so last night I updated to Sonoma 14.7.1 and Safari 18.1. Same negative result.

Interestingly, there were several threads of similar problems from 2020 and at least one from 2022. Some people gave workarounds, others said they didn't work, and there was some consensus it was a server-side issue. But there must be more to it than that, or we'd be having some "me too" responses here!
 
Back
Top