Problem using session

Scripts82 · December 14th, 2006, 12:06 PM

Hi, need some help here with sessions...
I'm facing some problem using session for my login page for my web application...
In other pages, I don't have any problem and I'm not sure why.

What is supposed to happen:
1. User Logs in (secure/login.aspx)
User id is stored as in session object
2. User redirected to account details (admin/acct.aspx)
User id is retrieved from session object and printed using response.write

Below shows part of the code i've used:

In login.aspx:

Code:

    FormsAuthentication.SetAuthCookie(Me.txtbox_LoginID.Text, False)
    Session.Add("LoginID", Me.txtbox_LoginID.Text)
    Response.Redirect("../admin/acct.aspx")

In acct.aspx:

Code:

    response.write(Session("LoginID"))

Problem: The Login ID is not printed! I did a step through of the code and the count for number of items stored in session = 0 when it should be 1!

I've used the above methods for other pages to store other types of values and they all work. But for this particular login page, it just does not work!

Any help is greatly appreciated!

Thanks.

Scripts82

dparsons · December 14th, 2006, 12:23 PM

What happens if you try to write this value to the screen:

Response.Write(User.Identity.Name.ToString());

-------------------------
I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.

^^Thats my signature

Scripts82 · December 14th, 2006, 12:44 PM

Hi dparsons, that works, in fact I have got around by using User.Identity.Name.ToString() and Request.ServerVariables("AUTH_USER")

However, my problem remained unsolved because I still need to pass other variables via the session object...

The code i showed is a simplified version...
The full code will first connect to a database, check the account type of the user and write some variables to the session object for use in other pages...

Any clues?

Thanks!

Scripts82

dparsons · December 14th, 2006, 12:50 PM

In so far as why your session object is empty i dont know, this is syntactly correct:

Session.Add("LoginID", Me.txtbox_LoginID.Text)

And, presumeably, it should have a value associated with it. It seems that there is a bug in your code somewhere that is setting this value to nothing. I am not sure. Like i said, the code you provided is accurate.

-------------------------
I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.

^^Thats my signature

Scripts82 · December 14th, 2006, 12:55 PM

hmm... yep... it seemed rather weird...

i'll keep trying till end of the day to see if i can get it working... otherwise i'll just find some other way to get by this...

thanks for the prompt reply!

Scripts82

Scripts82 · December 14th, 2006, 01:52 PM

somehow, after fiddling it worked... not sure why, but hope this last!

Scripts82

Scripts82 · December 14th, 2006, 02:01 PM

ok... i finally figured out why!

in my login form, at the Page_Load code, the i have the following code:

Code:

  Session.Abandon()
  FormsAuthentication.SignOut()

I've forgotten to enclose them in a "Not isPostBack" block and hence, the sessions keeps getting killed!

the final code that worked:

Code:

Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
    If Not IsPostBack Then
      Session.Abandon()
      FormsAuthentication.SignOut()
    End If
End Sub

Private Sub btnLogin_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnLogin.Click
    FormsAuthentication.SetAuthCookie(Me.txtbox_LoginID.Text, False)
    Session.Add("LoginID", Me.txtbox_LoginID.Text)
    Response.Redirect("../admin/acct.aspx")
End Sub

I guess sometimes when one is new, he'll need to learn things the hard way...

Scripts82

dparsons · December 14th, 2006, 02:07 PM

lol ya that would do it! =]

-------------------------
I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.

^^Thats my signature