Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Stop cached login for new tab

  • 1 reply
  • 1 has this problem
  • 4 views
  • Last reply by TyDraniu

more options

Hello, I've had this problem before I believe and I had to change something in about:config to rectify this issue but cannot find it nor know exactly how to search for it.

I have two Microsoft Online accounts, Account A and Account B.

When I go to a website I am prompted to pick an account and I can see Account A and Account B. I then enter my credentials for Account A and I'm in, great.

I then go to another site where I need to use Account B, but I don't have the chance to pick Account A or Account B because I'm presented an error because the new tab is trying to use Account A.

How do I stop this?

Hello, I've had this problem before I believe and I had to change something in about:config to rectify this issue but cannot find it nor know exactly how to search for it. I have two Microsoft Online accounts, Account A and Account B. When I go to a website I am prompted to pick an account and I can see Account A and Account B. I then enter my credentials for Account A and I'm in, great. I then go to another site where I need to use Account B, but I don't have the chance to pick Account A or Account B because I'm presented an error because the new tab is trying to use Account A. How do I stop this?

All Replies (1)

more options

Looks like you have to use a separate container for site B.