Persistent security across two IIS servers.


We're having a problem that the developer has suggested a solution to and we're not quite sure that's the right way of doing it and would like some input as to how we could resolve the issue.

So here's the synopsis of what we're doing currently:

We have a website that lives on one server.  Customers access it with their username and password.

This website at some point calls a second website (different IIS server) and performs some action(s).  

Then the second website returns the user to the first website for finalizing the business they were doing.

We have no choice in the multiple IIS servers.

We would like to keep customers who bookmark the link to the second server from re-accessing that URL after they close the browser and/or a time-out.  The developer suggested using Session ID's but I'm under the impression that the session ID would not be passed to the second server.  In addition the developer wants to create a SQL entry with a time-stamp of when this URL expires, but honestly I think we rather just have it expire when the client closes the browser.

So, to the question I think I'm asking.

Is there a cleaver way of making a URL ONLY work once.   I see ways of passing a UniqueIdentifier or something but is that the way to go?

We can't trust users pressing a "Logout" button, so it somehow has to be done by the site.

It's written in C# with visual studio 2013.

Thank you
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dave BaldwinFixer of ProblemsCommented:
When this question came up before, I believe the solution was for the second server to query the first server to see if the user was currently logged into the first one.  If they are logged in, proceed.  If not, deny access.  That way all the tracking is done only on the first server.  You might even redirect them to the login page on the first server if they try to access the second server directly.  Cookies and/or SESSION data can be used to do the tracking.  Note that the second server will not be able to 'see' the session cookie for the first server.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
prositAuthor Commented:
I'll give you the points since no one else cared... EE used to be better than this!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Development Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.