How to Log Into a Web App Simultaneously with Different Account?

How to Log Into a Web App Simultaneously with Different Account?

I want to log into a web application, using at least ten account names at one single point of time ( I am not trying to do anything illegal, so don't worry). AFAIK, each tab in Chrome will share the same session, therefore, for one machine, one can use Google Chrome to log in at most 2 accounts, one in normal mode, another in Incognito mode.

Asked by: Guest | Views: 421

Total answers/comments: 3

Comments display order:

bert [Entry]

CookieSwap to change users in just one firefox.

bert [Entry]

"Use Firefox with the -no-remote option as many times you need

Problem is, you have to open several Firefox processes, the cookie swap extension seems better"

bert [Entry]

"As it's on localhost the solution is really simple: add dummy domain names to your hosts file, like:

127.0.0.1 localhost dummy1 dummy2 dummy3

Or:

127.0.0.1 localhost
127.0.0.1 dummy1
127.0.0.1 dummy2
127.0.0.1 dummy3

All these dummy domains will have their own cookie, and thus their own session. And the tabs or windows will be easily distinguished from one another, based on the URL you see. (Of course, this assumes the session is based on a cookie, but your testing using multiple browsers shows that is true.)

(You may also need to tell your web server to map requests for those dummy domains to the same ""virtual host"".)

When this would not have been your own server, or one that was not easily changed to handle requests for additional domains, then using multiple web-based proxies like listed on Privax might do the trick as well. Though I guess I'd prefer -no-remote with Firefox then."
"As it's on localhost the solution is really simple: add dummy domain names to your hosts file, like:

127.0.0.1 localhost dummy1 dummy2 dummy3

Or:

127.0.0.1 localhost
127.0.0.1 dummy1
127.0.0.1 dummy2
127.0.0.1 dummy3

All these dummy domains will have their own cookie, and thus their own session. And the tabs or windows will be easily distinguished from one another, based on the URL you see. (Of course, this assumes the session is based on a cookie, but your testing using multiple browsers shows that is true.)

(You may also need to tell your web server to map requests for those dummy domains to the same ""virtual host"".)

When this would not have been your own server, or one that was not easily changed to handle requests for additional domains, then using multiple web-based proxies like listed on Privax might do the trick as well. Though I guess I'd prefer -no-remote with Firefox then."