Using command to open a vault in another tab forces me to re-enter my password

... but I don't need to re-enter the password when I keep things inside the same tab.
That feels a bit inconsistent. Is this a bug or a design decision?


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided
Referrer: kb:undefined, kb-search:sound

Comments

  • Hey @steipete! Great question. That's a security feature. Currently, it's not possible to maintain the session beyond the tab you have opened because everything is encrypted. We've been looking into a way to make this possible within the same browser possibly using the native app, but it's a lower priority issue at the moment. You can always use the native apps as a sort of second tab. :)

  • steipete
    steipete
    Community Member

    Oh, very interesting. How does that work? Is there anything to read up? Everything handled inside JavaScript?
    You could probably add a crypto token in combination with localStorage, but these are just random ideas, not the JS expert here.

    Thanks for the explanation. I'll just learn to live with it.

  • @steipete Thank you for the feedback!

    You are correct. The entire state of the app, including the encryption keys are stored in the browser memory. We would not want to store it in the localStorage or persist in any other way.

This discussion has been closed.