Thank you Jack_P_1P for your reply.
Sorry for the delay in responding we have been under a significant time crunch how we have no working 1Password on any laptop. We have been forced to type in very long (24+ character) passwords by hand from iOS devices or an excel spreadsheet. Being down for 2.5 week is taking its toll and many things are taking much longer.
I don't want to duplicate details of our on-going tech support case [#GWB-59355-691], so I invite you to investigate that case if you are interested in the fine details. Nevertheless, to answer your questions, I need to go into some additional details.
Please do NOT consider the following test to be a support request The following is just some context in an effort to answer your questions.
Still, we appreciate your question and so let's respond in general for those who may be reading this thread and wondering what is going on:
Firstly I'd like to say that I absolutely understand how frustrating this is. We don't like seeing people lose data either, so we're happy to continue working with you.
Thank you, Jack.
BTW: I still want to work with support to resolve this matter. Moreover, if Agile is interested, I would like, from an outsider's perspective, to understand how this disaster happened in the hopes that things could be fixed OR in the case of things being "my fault", how people might avoid my mistake.
Suggestion: When someone is selecting the "3-year subscription deal" that the 1Password app was offering, ASK permission or otherwise make it VERY CLEAR that approving the deal includes migrating any local vault to 1Password.com. Perhaps detect if there is a local vault and before it is too late, give them a clear pop-up of the form:
To proceed, we first need to move your local vault to 1Password.com. Do you wish to proceed? {YES) {NO}
... with the default being NO. There may be legal, contractual, or personal reasons why someone might not be able to move their vault to 1Password.com at this time. Don't just assume it is OK to migrate. Obtain a very explicit permission before you do.
I am not anti-1Passowrd.com by any means. I have 4 vaults on 1Passowrd.com in addition to an iCloud synced local vault. I am just suggesting that moving such a local vault to 1Password.com should have been an EXPLICIT decision: one that I might have delayed a few weeks until I was ready, had I known.
Suggestion: Do not offer a "3-year subscription deal" "personal license" to someone who already has a "family license".
If someone already has a "family license", offering them a "3-year subscription deal" for a "personal license" might not be a good thing.
In my case I had an existing "family license" vaults in 1Password.com. When I accepted the "3-year subscription deal" I was given a "personal license", not an extension on our "family license". Part of the start of that "3-year subscription deal" "personal license" was the creation of a new personal vault containing the migrated local vault keys.
I used the same Email address for this "3-year subscription deal" "personal license" as my "family vault" Email address. Again, thinking that I was extending the "family license" time 3-years, I gave it the same Email address. When I saw that the secret key being used was the same as my "family license", I gave it the same password as my 1password.com login.
BTW: I also have a vault set from my former employer in 1Password.com (with my former employer's permission of course).
Again, I had these vaults in 1Password.com:
- Previous employer (company license: 2 vaults: Shared and Private) [ -- edited by 1Password staff -- ]
- LANDON NOLL'S FAMILY (family license: 2 vaults: Shared and Private)
- in addition to a local iCloud synced vault.
After accepting the "3-year subscription deal" I had:
- Previous employer (company license: 2 vaults: Shared and Private) [ -- edited by 1Password staff -- ]
- LANDON NOLL'S FAMILY (family license: 2 vaults: Shared and Private)
- LANDON NOLL (personal license: 1 Private vault - contain the migrated keys from the local iCloud synced vault)
- No local iCloud synced vault on the "primary laptop" (the local vault was still on the "backup laptop" and iOS devices)
I was able to use the 1Password app on macOS, and use my existing "master unlock password", and login to 1Password.com, and see my 576+1 items on 1Password.com under the "LANDON NOLL" vault.
This state lasted somewhere between about 24 to 48 hours. Then on day 2, the LANDON NOLL vault vanished. Moreover, the 1Password app no longer recognized my "master unlock password" on my "primary laptop". Worse still, the 1Password diagnostic app produced an *empty diagnostic report folder: as if there was no vault data for it to even diagnose.
QUESTION: Could the use of the same Email address and password for the "family license" and that new "3-year subscription deal" personal VAULT led to that new vault being seen as a duplicate and removed?
BTW: I say 576+1 items. The +1 is the additional item that is added to the vault when it is migrated.
BTW: When support directed me to migrate the local iCloud synced vault on my "backup laptop" to 1Password.com, I chose, as I was instructed, to migrate those items into the private vault under LANDON NOLL'S FAMILY "family license".
The 576+1 items migrated from local iCloud synced vault on my "backup laptop" to 1Password.com just fine.
For the next 24 to 36 hours, I was able to use the 1Password app on my "backup laptop" just fine. I could also login to 1Password.com and see the 576+1 items that migrated to the private vault under LANDON NOLL'S FAMILY "family license".
Then (after 24 to 36 hours), the "master unlock password" failed to unlock the 1Password app on the "backup laptop". I.e., this was the 2nd time that there was a DELAYED loss of being able to unlock the 1Password app on a mac.
Unlike the 1st failure from the "primary laptop" where the 1Password diagnostic app produced an empty diagnostic report folder, on the "backup laptop" the 1Password diagnostic app WAS able to produce a diagnostic report (that I gave to support).
QUESTION: Any idea on why these disasters were delayed? I.e., why things worked very well for 24 to 48 hours before disaster struck? Is there some background process on the 1Password.com back end that is involved in these disasters?
With that said, would it have been possible that you used a different account password for your 1Password account compared to your Primary vault password?
Yes.
The "master unlock password" (or Primary vault password if you are referring to what I call "master unlock password" ) (that I use with the 1Password app on the mac and iOS decides) is NOT the same as my "1Password.com login password".
There is an extremely important separation whereby the "master unlock password" CANNOT be the same as my 1Password.com login password! So Yes, the are different by design and requirement.
BTW: I tried also using the "1Password.com login password" to try and unlock the 1Password app: no success.
1Password accounts have a slightly longer password requirement than the Primary vault password did, and if you had migrated all your vaults to a 1Password account, then removed your standalone vaults from 1Password, 1Password would no longer unlock using your Primary vault password, but your 1Password account password instead.
Interesting / good question:
The "master unlock password" is 14+ "j-random" characters that was generated by the 1password app containing UPPER chars, lower chars, digits, symbols, no words, no repeating patterns, etc.. Just a solid j-random password.
The "1Password.com login password" is a 25+ "j-random" characters that was generated by the 1password app containing UPPER chars, lower chars, digits, symbols, no words, no repeating patterns, etc.. Just a solid j-random password.
I believe both passwords are of sufficient quality. The "1Password.com login password" is longer than the "master unlock password" by 11 characters.
Just to verify that all of your items are still as expected, are you able to sign in to your account on 1Password.com using your 1Password account password, not the password you may have used previously to unlock the 1Password app?
Yes. I have always been able to login to 1Password.com using my "1Password.com login password".
Even when, the " LANDON NOLL (personal license: 1 Private vault)" vault disappeared, I was able to login to on 1Password.com using my "1Password.com login password". I re-verified this just now.
((continued on next post))
