3831 Views 5 Replies Latest reply: Jun 3, 2010 11:57 AM by Marc van Maastricht
Yes, everything in that tab is turned on. I tried to manually add the information to my keychain, making a new saved password for all three of the URLs that the page loads content from. As far as I understand, Safari could/should recognize at least one of those URLs and try to fill in the name/password associated with it, but no, nothing gets filled in. ...and I checked, I never told Safari not to save my password for that site.
Firefox is able to save the form information without any special action on my part; I used firefox to log in once and my information was saved. I didn't need to specify the information should be saved, nor did I need any special plugins (to bypass "autocomplete=off" settings, for example—there are none on the page).
When I go to this log-in page, I can tell Safari to auto-complete the form, and it fills in my first name and last name from Address Book with no password. I think this might be the problem, since the page asks for a first and last name (from a game, not my real name), so Safari seems to think it's just asking for my real first and last name. :/
I haven't rebuilt my system since.... well.... ever.... Not on this laptop, anyway, and it's three years old. I was going to say not since Time Machine backups, but I've never even restored my system using Time Machine.
Safari is still saving my info, just not on this one log-in page, and I think it's because it's like a form (with first name, last name) AND like a log-in page (with the password).
If I have to start over with everything.................... No, Safari won't be the thing that finally forces me to rebuild! xD
I've had the same problem and it has everything to do with Code Signing: the way Mac OS X checks if applications can have access to secret data (in Keychain Access). Safari uses this too and if Code Signing is somehow broken; strange things happen with saving or not saving passwords.
You can check Code Signing for Safari in Terminal:
codesign --verify --verbose /Applications/Safari.app
...If the result is different from:
/Applications/Safari.app: valid on disk
/Applications/Safari.app: satisfies its Designated Requirement
...then something is wrong.
There are complex ways to change the Safari code signing, so just take the easy way: just put your Safari application in the trash and copy the complete (working) Safari application from another Mac (with the same version number) to yours (or from a Time Capsule version of Safari from the period everything was nice and easy).
After starting the copied version of Safari, Keychain Access will ask you for permission. Choose "always" and you're problem is fixed!
It did the trick for me after Googling and troubleshooting for hours...