Two Logons Required -- why?

tedd

Hi:

The most recent update (Version 5.1) now requires me to first enter my password to open the main application, which shows me all my accounts, but before it will open any account I have to re-enter my password via a pop-up window. This two-step entry is pointless and annoying. Clearly this is a bug in the software. What are you doing to fix it?

Thanks,

tedd

Stephen_C

I suspect nobody else is seeing what you see as nobody else has mentioned that problem. That means it's most likely not to be a bug but a problem unique to you.

I think a rather fuller explanation of what you're seeing would be helpful—particularly if you're able to include a screen shot of the "pop-up window" (so long as it doesn't contain confidential information, of course).

What I understand so far is that in 1P for Mac 5.1 you enter your master password. At that stage you're not able to do anything else in 1P without entering the master password again. Is that correct?

Stephen

hawkmoth

Edit: I answered this question while thinking it applied to iOS. The original post is in the Mac forum, so what appears below is not germane, unless the post is indeed about iOS, not OS X.

@tedd - If you don't have the option set to use a PIN or Touch ID (for devices capable of using Touch ID), you will get the behavior you describe. If you have one of those options enabled, your master password gets saved to the iOS keychain, from where it can be passed to the 1Password extension. Then you don't have to reenter your master password in that popup. But if you don't use the PIn or Touch ID, your password isn't stored and you will have to reenter it.

I know this because in my iPad I don't have a PIN set, and I also have to reenter my master password when I invoke the extension. I do it this way to make it easier to remember my master password by having to use it each time I open 1Password on my iPad. I was puzzled like you are, and what I describe here is the answer I received when I asked. If I add a PIN, neither the master password, nor the PIN are required during the interval I've set in the security settings.

Stephen_C

I'm still a little puzzled in spite of hawmoth's comments (which are exactly right if you're talking about 1P for iOS). However, as you posted on the 1P for Mac forum and refer to 1P 5.1 I thought you must be talking about 1P for Mac—in which case everything I said in my post above stands. :)

Stephen

hawkmoth

Oops! I didn't notice I was in the Mac forum. :p

I'm going to leave my answer for now, in case this really was about iOS. I'm hoping @tedd will return to let us know. I'll edit my post then.

littlebobbytables

@tedd,

Please do read Stephen_C's post, #2, as we would also be quite curious to learn more about what you're experiencing. Certainly I've only ever had to enter my Master Password once.

Now if you reply saying you unlock the vault and then seconds it is once again locked that sounds like a behaviour we've observed if there are two copies of 1Password on a Yosemite. There's an 'quirk' in Yosemite where it doesn't always load the correct 1Password mini. If this is what you're experiencing then simply deleting the other copy of 1Password and rebooting your Mac will sort it out. Normally users get a small warning from 1Password to say there are two copies but not always. The issue is just with Yosemite and we're reliant on Apple for the fix.

Either way, we'll be curious to hear back from you.

tedd

Hi all:

Update.

I turned off the Safari extension for 1Password and logged off my Mac.

When I logged back on, I was presented with a 1Password Crash Report, which I filled out and sent. After that, all problems went away and everything worked as it did before the problem.

FYI, I didn't see a need to provide screen shots, I think everyone knows what a standard 1Password logon looks like as well as what a 1Password pop-up looks like -- what would be the point?

In any event, the problem has disappeared -- a software fart I assume.

Thanks for everyone's help.

Cheers,

tedd

Drew_AG

Hi @tedd,

Thanks for the update! That's good news, I'm glad it's now working correctly for you. I don't think we've had any other reports of the issue you described, so I don't know what would cause something like that. If the problem comes back or you need anything else, please do let us know. Thanks! :)