Safari Extension 1 Password Panel

Jonathan_YOW

<div class="IPBDescription">Re-entering master password several times</div>Been using 1 Password quite happily prior to the Lion upgrade. Just an observation - on an intermittent basis I am being prompted to enter my master password in the Safari extension password panel (which fails to unlock the panel) - and then prompted to reenter the same master password in the main 1 Password app - which I then have to re-enter in the Safari extension password panel to unlock. Any idea why this is occurring?



Thank you.

khad

It sounds like 1Password is automatically locking per your security settings ([b]1Password > Preferences > Security[/b]).



If entering your master password fails to unlock the Safari extension, [url="http://help.agilebits.com/1Password3/troubleshooting_safari_5.1.html#1password_extension_wont_unlock"]it could be related to Private Browsing[/url]. Please disable Private Browsing and then relaunch Safari.



If that does not apply to your situation, you may need to [url="http://help.agilebits.com/1Password3/troubleshooting_safari_5.1.html#extension_data_does_not_match_the_main_application"]reinstall the extension[/url].



I hope that helps. I am not able to reproduce the problem here, but are there any certain repeatable steps I can take to get this to occur on my own machine? Please let me know how it goes and what you discover.



Thanks!

Jonathan_YOW

Thanks for the quick response. I have the security settings with the Lock settings all enables - the unlocking setting at "Disable automatic unlock for 1Password". As I mentioned, this is an intermittent issue - when I am prompted to type the master password in the browser it does not take, and prompts me to type the password in the main application, which I then have to retype in the browser. this morning, logging into Agile forums I was only prompted to type the master password in the browser.

khad

Could you please try the new Beta release (3.7.0.BETA-2) and see if it fixes this problem? You can do this by going to the 1Password > Preferences window, selecting the Update panel, enable the "Include Beta versions" checkbox, and then click Check Now. Once the update is installed, try again and see if it helps.



Thanks!

Jonathan_YOW

So been trying out the new Safari extension, very nice, greatly improved - well done.



Even with the most recent updates of the extension and the app, still experiencing the password issue. As a reminder, if I open Safari and then try to access the extension, I am asked to open the 1PW app and enter the password - I then have to re-enter the password in the extension. This occurs only when I've started up my machine or left it for some time asleep. I do have the auto-lock after 20 min set in the 1PW app.



I just can't figure out why if I enter the password in the extension that this does not allow full access to my data, whether the 1PW app has been opened or not.

Jonathan_YOW

....and as a follow-up - this morning I turned in my computer and the following steps were required:



1. Opened Safari

2. Typed sft-cmd-\ to access a website.

3. Extension opened and asked me for the master password.

4. Entered the password.

5. Extension button red (attached), with message "data not available - please open and unlock 1 Password app to update extension data".

6. Opened 1Password app and entered password.

7. Returned to Safari and typed sft-cmd-\ to access the website from step 2.

8. Extension window did not even open this time.

9. Tried a couple more time - no extension window.

10. Shut down Safari and reopened.

11. Typed sft-cmd-\ and was finally (!) able to access a website.



Seems like way to many steps. The previous 1Password simply required steps 1-4. I have installed and reinstalled the extension several times - have everything up to date etc. Please advise.

khad

This is definitely not expected behavior. We just made some improvements to the syncing between the Safari extension and the main application. There are even more improvements coming in the next beta, but could you try the latest beta version 3.7.2.BETA-2 and let me know if that helps in conjunction with version 3.7.b10 of the Safari extension? You didn't mention which versions you were using, and we have been updating both the application and the Safari extension at a steady clip lately. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



Also, please try uninstalling the Safari extension, and then quitting Safari using Option-Command-Q to quit and discard windows. (You may want to bookmark some sites before you do this). This will clear some caches and will likely get things working for you. [url="http://help.agilebits.com/1Password3/safari_install_update.html#how_to_install_the_new_safari_51_extension"]Then reinstall the extension carefully following the steps in the User Guide[/url]. [i]Each step in the Use Guide is important especially if you are having trouble getting it working.[/i]



If you are still having trouble, could you please email us your Diagnostics Report? To generate the report from 1Password on your Mac, open 1Password and select Help > Troubleshooting > Diagnostics Report. Then attach the entire file to an email to support@agilebits.com.



Please include a link to this thread in order that we might more quickly "connect the dots" when we see your Diagnostics Report in our inbox.



[color="#FF0000"]Please do not post your Diagnostics Report in the forums, though.[/color]



Please let me know in your reply to this thread or via PM when you have sent the DR, and I will take a look as soon as possible.



Thanks!

Jonathan_YOW

Thank you, that seems to have worked.

Ben

Great! Thanks for the update. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />

Jonathan_YOW

I spoke too soon. Same issue has cropped up. I'll send through the diagnostic report.

khad

We are pushing an update very soon which should resolve this once and for all. The issue was much more persistent in some cases than others, but we re-worked the way in which the browser extension communicates the background process, so this will hopefully be a thing of the past very soon.



I am going to send you a PM with further instructions.