Security

Re: Scope of User object

DotNetAdvisor — Fri, 09 May 2008 20:41:13 GMT

Hey no problem.

Also, can you mark this thread answered so I don't keep checking on it? Thanks.

Re: Scope of User object

Skychan — Fri, 09 May 2008 20:38:30 GMT

Thank you so much! I truly appreciate your help!

Re: Scope of User object

DotNetAdvisor — Fri, 09 May 2008 19:58:34 GMT

You can access pretty much everything you need through the HttpContext class. It exposes static properties for the current thread. If you want to get the username of the current thread access it this way:

HttpContext.Current.User.Identity.Name

Scope of User object

Skychan — Fri, 09 May 2008 19:27:02 GMT

I want to have access to the User object everywhere in my application. I don't understand why the Session and User object are not available to domain logic classes. Clearly there is always only one session and one user when the running thread is executing application code. The session and user belong to the thread (and should be treated as application global objects). There is no way to access the wrong session or the wrong user. So why are they restricted to only .aspx pages? .ascx pages don't even have access to the User object, but thankfully I have access to the Session there so I just place the User within the Session.

Can someone please help me get access to the User object from domain logic classes?

thanks :)

Skychan