Workflow Soluiton

 View Only
  • 1.  Web page cannot be used by more than one person at a time

    Posted Jun 20, 2013 10:54 AM

    I have developed a web page that uses the Get Current User component to identify the user.  Their logon Id is then used to pull the list of computers associated with it.

    I'm finding that if the site is being accessed when a second user logs on, the information from the first user is displayed to the second user.  Can anyone explain why this might be happening?  The application won't be very useful if only one person can access it at a time.



  • 2.  RE: Web page cannot be used by more than one person at a time

    Posted Jun 20, 2013 11:52 AM

    Couple of questions - how do you have the getcurrentuser item configured? Is it set to HPPTContext? or somethig else? Also, did you update the WebConfig file to use Windoiws Authentication?

     

    Second, how are you storing the resuting user from the GetCurrentUser? Are you putting it in a global varaible?

    rob



  • 3.  RE: Web page cannot be used by more than one person at a time

    Posted Jun 20, 2013 02:04 PM

    When deployed the GetCurrentUser is set to HTTPContext and the Web.config file is updated to Authentication Mode = 'Windows'.  The output of the GetCurrentUser is in a global variable.

    The output of the GetCurrentUser is a variable named CurrentUser.  I take this variable and strip off the domain to derive a variable named CurrentUserWODomain.  What I've seen is that the CurrentUser has the correct value but the CurrentUserWODomain has the value from the other session.



  • 4.  RE: Web page cannot be used by more than one person at a time

    Posted Jun 20, 2013 03:11 PM

    Just to clarify, when I said I was using global variables I meant that they are visible throughout the project rather than being visible only within an Embedded Model. 



  • 5.  RE: Web page cannot be used by more than one person at a time
    Best Answer

    Posted Jun 20, 2013 03:31 PM

    It turns out that the Embedded Model that used the CurrentUserWODomain to build other objects and variables had Caching turned on.  I turned off Caching and it seems to have resolved the issue.

    Thanks for your help.