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

When spanning new tabs (firefox) my users are asked to re-authenticate with pages already signed into. Can you tell me how to fix this issue for firefox users?

more options

With some research I found regedit setting called “TabProcGrowth” that allows tabs to span without re-authenticating with certain browsers. Can you tell me how to fix this issue for my Mozilla Firefox users? Our current version of Mozilla Firefox is: 24.5.0 (x86 en-US). This was first noticed with a product called Confluence that we use in our Tech Support area. Users are having to reenter their password every time they click on a new link in confluence. Any help would be appreciated.

Thank you,

With some research I found regedit setting called “TabProcGrowth” that allows tabs to span without re-authenticating with certain browsers. Can you tell me how to fix this issue for my Mozilla Firefox users? Our current version of Mozilla Firefox is: 24.5.0 (x86 en-US). This was first noticed with a product called Confluence that we use in our Tech Support area. Users are having to reenter their password every time they click on a new link in confluence. Any help would be appreciated. Thank you,

All Replies (3)

more options

This is an odd problem: server apps generally do not care whether pages are being opened in the same tab or a new tab, as long as the same cookies are sent. In fact, how would the site even know, since the request should appear to be identical?

If you are using private browsing mode, there might be an issue with cookies saved in one window being sent in a different window, but tabs in the same window definitely should draw from the same cookie jar.

I guess one difference is that a request for a linked page includes a header indicating the referring page. Is there any possibility you are blocking that information?

Can you think of any reason for other authentication-related information to change, such as the IP address associated with the request?

more options

Hello,

Thank you for your speedy reply! You make a good point; I have one question which pertains to your response (i.e. Is there any possibility we are blocking this information?). Yes - Recently our helpdesk internet access was removed. With that said; That would mean ports 80 and 443 access has are not routed outside our company, could this have caused our Confluence logon new tab issues that calls 443 but internally to our company?

Thank you again,

more options

Hi Bernie:

As long as you are accessing your internal server on http:// or https:// then I would expect the normal rules to apply. To see whether some external requests are being blocked, you might try using Firefox's Web Console, Network tab.

You can open the console in the lower part of a tab using either:

  • Ctrl+Shift+k
  • "3-bar" menu button > Developer > Web Console
  • (menu bar) Tools menu > Web Developer > Web Console

Click "Network" on the top bar of the Web Console.

Then use the address bar or a bookmark to launch Confluence in the same tab. Each request made by Firefox should be displayed along with the result. You can click a row for more details.


When I look up "TabProcGrowth" it seems related to the Protected Mode feature of IE8 and newer, which is not (yet) applicable to Firefox. http://blogs.msdn.com/b/askie/archive/2009/03/09/opening-a-new-tab-may-launch-a-new-process-with-internet-explorer-8-0.aspx

However, if Confluence is heavily reliant on plugins such as Flash or Java, that could be a factor because plugins are run out-of-process in Firefox. In that case I suggest checking with Confluence for suggestions.