Closed Bug 1511882 Opened 7 years ago Closed 7 years ago

Lockbox saves login data to wrong profile

Categories

(Firefox :: Untriaged, defect)

65 Branch
x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox65 --- affected

People

(Reporter: jmccrosky, Unassigned)

Details

I typically have two browser instances running with two different profiles. I launch the second instance by navigating to "about:profiles". Since installing Lockbox iOS, I've discovered that saved logins from my second profile are usually (but not always) saved to my first profile. The "Saved Logins" button in preferences reveals an overlapping but different set of saved logins in each of the profiles. In iOS I only see a small subset for the second profile. Happy to provide more information as needed.
Please provide us a link to install the LockBox iOS for Mac app. Is this a Firefox for Mac OS issue or a Firefox for iOS issue? Thank you for your contribution!
Flags: needinfo?(jmccrosky)
Sorry, I'm not sure what you mean by "a link to install the LockBox iOS for Mac app". LockBox iOS is available on the Apple App Store. I believe it is a problem with multi-profile support in Firefox for Mac OS. I only mention LockBox iOS as it was when I installed it that I was able to see the set of saved logins for each of my Firefox accounts.
Flags: needinfo?(jmccrosky)
This is the LockBox app on the App Store: https://itunes.apple.com/us/app/lockbox/id285681310?mt=8 Is this what you are using? This is an app for iOS, not Mac OS X. Are you having problems with the passwords saved on the Desktop Mac operating system? Or do you have problems with the passwords saved for the Mobile iOS operating system on an iPhone or iPod?
Flags: needinfo?(jmccrosky)
Sorry if I was unclear. Yes, I am using Firefox Desktop for MacOS and LockBox App for iOS. I believe that the problem is that Firefox Desktop for MacOS, when I run two instances with different profiles and different Firefox accounts, is saving the logins to the incorrect account. I can see clearly which logins are saved to which account, as LockBox App for iOS allows me to login to one specific account and see the saved logins there.
Flags: needinfo?(jmccrosky)
I have tried to reproduce the issue using the following steps on MacBook Pro 2017 with Mac OS 10.13.6: 1. Used the terminal to open 2 different instances (2 different running profiles) of the same Nightly browser. 2. Logged with different Firefox Sync accounts on each of the two instances. 3. Saved a bunch of random passwords on each of the instances. 4. Restarted both instances. 5. Checked whether the saved logins are the intended ones in each of the two instances. The correct credentials were saved on each instance; Issue did not reproduce. Considering all the above, we need some more information in order to reproduce your issue: a. Do you usually have the same Nightly browser opened twice using the terminal and the "-no-remote" command option? If no, then how do you open 2 different profiles, exactly? b. Do you have different Firefox Sync accounts on the 2 different opened profiles of Nightly? c. If you open each of the 2 profiles and check the credentials saved, not from the LockBox app, but from the "Saved Logins..." modal, from the "Logins & Passwords" subsection of the "Privacy & Security" section of the browser's preferences, are they the correct ones saved? Or are there the same credentials shown as in the LockBox app? Thanks!
Flags: needinfo?(jmccrosky)
Now when I attempt to reproduce, it seems to work fine. I'm not sure what happened before (I definitely have some logins I've only used in my personal profile synced with my work FxA). Maybe I was logged in with the wrong FxA in my personal profile before. The only difference between my workflow and your reproduction attempt is that I open the second browser instance using about:profiles and the "Launch profile in new browser" button. Resolving this bug. Thanks for looking into this!
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(jmccrosky)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.