OW Sneaky Peeks and keychain
 

It is still in the release notes that saving to the keychain may not work. I have yet to see this work properly with any of the SP builds.

I also note that reading [I]from[/I] the keychain also may not work. When the transition was made from .dotmac to mobileme, the authentication changed to go through auth.apple.com. Under MacOS 10.4.11 or 10.5.4, the mobileme login password cannot be saved via OW. However, I manually created the correct password entry using Keychain access. OW sneaky peeks will only autofill the entry properly from 10.4.11 keychain and will not fill from the 10.5.4 keychain. The entries are identical, and the overall keychain prefs are the same. 10.5.4 also prompts to save the PW every time, so it's not seeing the PW at all.

Craig

I second that. One of the reasons I like to use OW rather than Opera or Firefox is the keychain. Without the integration working properly, I can’t really stay on OmniWeb.

Any official word about it? What is the problem? It used to work before, after all …

Cheers,
-Sascha

I believe the problem is related to Code Signing of OmniWeb, The fix will be included in the final 5.8 release. If it's preventing you from using OmniWeb you can always go back to 5.7.

Sorry for the inconvenience this can cause.

[QUOTE=troyb;45048]I believe the problem is related to Code Signing of OmniWeb, The fix will be included in the final 5.8 release. If it's preventing you from using OmniWeb you can always go back to 5.7.

Sorry for the inconvenience this can cause.[/QUOTE]

Thanks, Troy. Is this the cause of failure to read from the keychain under Leopard, also?

Reading should work fine. On the authentication page for me.com, I was able to successfully save credentials in OmniWeb 5.7 and then have them restored in the sneaky peeks.

Thanks for the heads-up, Troy! Much obliged. :)

Cheers,
-Sascha

Thanks, Troy. I tried rolling back to the release version, and it works as expected. The behavior I observed might have something to do with how the keychain entries themselves were formatted. My 10.4 keychain shows this item is an "Internet Password" and the 10.5 keychain item is a "Web Form Password." When I manually created these entries, I used the 10.4 syntax, and OW doesn't like this syntax in Leopard.

This may seem strange but iv'e noticed recently there are many of my web form passwords missing from keychain. Im not sure if it is a result of the SP release but they sure were in keychain before this release.

OmniWeb never deletes anything from your keychain. Safari however can if you use the "Reset Safari" option.

OW's Keychain process BUGS me!!!
 

Troy,

I save my important passwords in a separate keychain for easy maintenance. both Safari and OW can see them and use them to automatically fill fields. the problem though is that OW will *always* ask me if I want to save the passwords even though they're already in the keychain. Omni once told me that this is a problem with the OS and Keychain Access, but this *does not happen* with Safari. it's a pain-in-the-neck to always have to click on the Don't Save button.

furthermore, OW *can* delete passwords from the Keychain. if you click the Never button, OW deletes the (first) existing password from the Keychains, replacing the Account value with "Passwords not saved" and deleting the password. so OW can access the keychain and find the key to fill the fields, but cannot see that the key exists to not ask about saving the value, but can see the key to replace and delete it!

theoretically, OW shouldn't be looking into the Keychain to see that a key should not be saved for a particular web site. that preference should be saved in the site's preferences. no?

please fix this, SOON! I've just come back to OW from Safari to see if there have been any improvements in speed and response, but this password thing REALLY BUGS ME!!!

cheers,
Gregory