Home/ Questions/Q 7567941
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T14:47:46+00:00

I’m using Azure ACS in my ASP.net MVC 3 website (hosted in Azure too),

  • 0

I’m using Azure ACS in my ASP.net MVC 3 website (hosted in Azure too), the scenario is this:
A user first enters my website and fills a one field form, then they need to chose a provider and login, but first I want to store the field value so when they come back from login I’m able to create a profile with this value for the loged in user.

So I believe when they first enter the site and then leaves to login and enters the site again those are two different sessions am I right? and that’s the reason the stored data using session state (through SQL Server) is not present when they come back after login am I right? if this is true what would be the best approach then? if not then I’m doing something wrong storing temp data right?

Thanks

UPDATE:
I have discovered that HttpContext.Application state works keeping the data, still I’m not sure if it’s a good idea to use it in a controller considering it’s in Azure, will it work on production properly??

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Another approach would be to save whatever data you need to pass around in the Database, and just pass around some ID that refers back to the database record. You’ll pass this ID to IP and back through wctx (as Mike mentioned above).

    This will solve the issue of limited length of URLs (in case your data is very large). Of course you would need to manage deletion of this data, but this shouldn’t be hard.

    • 0