Hi,
I have an application published to three separate environments: dev, test, and prod. Dev and test each utilize a single web and sql server. The production code is published to a web server farm which uses three web servers and a single sql server. The only difference in the web files are settings in the web.config (connection strings, compile debug = true/false, and my prod web.config has machine keys for the server farm).
I am able to log into the dev and prod at the same time (i.e. I can log into dev and prod using my username and they are hitting separate SQl server databases (prod_app_db and dev_app_db), but when I try logging into the test server I just get pushed back to the login screen as if my cookie was lost or my session timed out (it correctly throws a message when I enter the wrong credentials and I can see in the test sql server db my failed attempts.
Each application is hitting its correct sql db, but I cannot figure out why I cannot be logged into my test website and prod website at the same time.
Not sure how I should go about troubleshooting this since my dev env is working simultaneously, with prod but test is not. If I am not logged into the prod website then I can log into the test website, prod is unaffected by test - I can log in whether I logged in on test, but once logged in on prod test is kicked off. It does not matter if I use the same or different user accounts on test and prod.
Does anyone have any idea what may be causing this conflict?
Is there a log that I can view to determine what is causing the session to be lost / authentication to fail and return me to the login screen when I attempt to log into the test website while authenticated with the prod website?
The production web.config is the only one that has machine keys, dev and test autogenerate them (not using web farms) and dev works but test can't log in when authenticated to prod in my browser. I have yet to try across other browser sessions.