Persistent security across two IIS servers.

Posted on 2014-08-27
Last Modified: 2014-09-18

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
Question by:prosit
    LVL 82

    Accepted Solution

    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.
    LVL 2

    Author Closing Comment

    I'll give you the points since no one else cared... EE used to be better than this!

    Featured Post

    What Security Threats Are You Missing?

    Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

    Join & Write a Comment

    A Change in PHP Behavior with Session Write Short Circuit ( (Winter 2014)** With the release of PHP 5.6 the session handler changed in a way that many think should be considered a bug.  See the note …
    If I have to fix slow responding website my first thoughts are server side optimizations: the database may not be optimized or caching is not enabled, or things like that. We often overlook another major part of our web application: the client. We o…
    Use Wufoo, an online form creation tool, to make powerful forms. Learn how to choose which pages of your form are visible to your users based on their inputs. The page rules feature provides you with an opportunity to create if:then statements for y…
    Learn how to set-up PayPal payment integration in your Wufoo form. Allow your users to remit payment through PayPal upon completion of your online form. This is helpful for collecting membership payments, customer payments, donations, and more.

    729 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    21 Experts available now in Live!

    Get 1:1 Help Now