Best way to keep track of user-related info? [Opinions wanted]

From: Edward J. Stembler (ejstembler_at_hotmail.com)
Date: 11/13/03 

Date: 13 Nov 2003 07:21:13 -0800

I have an ASP.Net portal application which requires a user to login.
The user has a CompanyId associated with their profile in the
database. Once they successfully login, I want to store the CompanyId
for that user somewhere for later reference.

What is the best way to do this? Should, I store the CompanyId in an
encrypted cookie? In the Context object? Somewhere else?

Here are some assumptions: Each user has a CompanyId assigned to their
profile. Multiple users can log into the site. The site will need to
know the CompanyId eventually on various pages (or usercontrols) for a
given user. The site must keep CompanyId's seperate per user.

Relevant Pages

  • Re: Best way to keep track of user-related info? [Opinions wanted]
    ... > The user has a CompanyId associated with their profile in the ... Once they successfully login, I want to store the CompanyId ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • listing users by profile values
    ... I have several attributes I want to users, companyID for example, ... so I'm using the profile feature to do this and it works great. ... My web app is used by several distincit groups of users as defined ... I want to have access to user and user profile information ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Can related Access form fields autofill after 1 field is entered?
    ... Your order records should only store the CompanyID. ... You can then use a query or any number of various lookup methods to DISPLAY ... An easy way to do this is to use a ComboBox for CompanyID with a RowSource ...
    (microsoft.public.access.gettingstarted)