One client can't login to our site

[=?Utf-8?B?S2VsbHk=?=]

We just switched our web application from .NET 1.1 to 2. Once client can't
login out of several that have been successful. They enter a correct user
name and password, click the login button and they are redirected back to
login with no errors or login failure. The same login account works fine from
other machines at different locations.

This client had no problem logging in before we switched. The login
procedures are essentially the same except for the .NET version. They are
using an updated IE6 browser.

Here is what I'm doing:

Build ticket:
Dim ticket As New FormsAuthentica tionTicket(1, ".TICKETNAM E",
System.DateTime .Now, System.DateTime .Now.AddMinutes (30), False,
Session.Session ID)
Dim authCookie As New HttpCookie(Form sAuthentication .FormsCookieNam e,
FormsAuthentica tion.Encrypt(ti cket)) Response.Cookie s.Add(authCooki e)

Make session variables:
Session("LoginN ame") = prmLoginName.Va lue
Session("DocGUI D") = prmDoc.Value
Session("EmpID" ) = prmEmployeeID.V alue
If prmEmployeeID.V alue 0 Then
Session("UserCl ass") = "Staff"
Else
Session("UserCl ass") = "Client"
End If
Session("GetsCE M") = prmGetsCEMRpt.V alue
Session("GetsPA C") = prmGetsPACRpt.V alue
Session("GetsHO L") = prmGetsHOLRpt.V alue

Check for authentication and session value from the loading page:
If Request.IsAuthe nticated Then
If Session("LoginN ame") <"" Then

[Proceed with page setup routines if successful....]

Else
'Go back and login again
FormsAuthentica tion.SignOut()
Session.Abandon ()
Session.RemoveA ll()

Response.Redire ct(Server_Proto col(Request.Ser verVariables("S ERVER_NAME")) &
"webaccess/login.aspx")
End If

Else

Response.Redire ct(Server_Proto col(Request.Ser verVariables("S ERVER_NAME")) &
"webaccess/login.aspx")
End If

[Rockn]

Would they have the correct framework installed on their computer?

"Kelly" <Ke***@discussi ons.microsoft.c omwrote in message
news:68******** *************** ***********@mic rosoft.com...

>
We just switched our web application from .NET 1.1 to 2. Once client can't
login out of several that have been successful. They enter a correct user
name and password, click the login button and they are redirected back to
login with no errors or login failure. The same login account works fine
from
other machines at different locations.

This client had no problem logging in before we switched. The login
procedures are essentially the same except for the .NET version. They are
using an updated IE6 browser.

Here is what I'm doing:

Build ticket:
Dim ticket As New FormsAuthentica tionTicket(1, ".TICKETNAM E",
System.DateTime .Now, System.DateTime .Now.AddMinutes (30), False,
Session.Session ID)
Dim authCookie As New HttpCookie(Form sAuthentication .FormsCookieNam e,
FormsAuthentica tion.Encrypt(ti cket)) Response.Cookie s.Add(authCooki e)

Make session variables:
Session("LoginN ame") = prmLoginName.Va lue
Session("DocGUI D") = prmDoc.Value
Session("EmpID" ) = prmEmployeeID.V alue
If prmEmployeeID.V alue 0 Then
Session("UserCl ass") = "Staff"
Else
Session("UserCl ass") = "Client"
End If
Session("GetsCE M") = prmGetsCEMRpt.V alue
Session("GetsPA C") = prmGetsPACRpt.V alue
Session("GetsHO L") = prmGetsHOLRpt.V alue

Check for authentication and session value from the loading page:
If Request.IsAuthe nticated Then
If Session("LoginN ame") <"" Then

[Proceed with page setup routines if successful....]

Else
'Go back and login again
FormsAuthentica tion.SignOut()
Session.Abandon ()
Session.RemoveA ll()

Response.Redire ct(Server_Proto col(Request.Ser verVariables("S ERVER_NAME"))
&
"webaccess/login.aspx")
End If

Else

Response.Redire ct(Server_Proto col(Request.Ser verVariables("S ERVER_NAME"))
&
"webaccess/login.aspx")
End If

[Mark Rae [MVP]]

"Rockn" <Ro***@newsgrou ps.nospamwrote in message
news:ud******** ******@TK2MSFTN GP05.phx.gbl...

Would they have the correct framework installed on their computer?

Clients don't require the .NET Framework to use ASP.NET web apps...

Just a (reasonably) modern browser...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

[bruce barker]

check if cookies are turned off. you can also detect this problem on the
server by settiing a cookie and redirecting to a page that test if a
cookie exists. say in your redirect add login.aspx?cook ie=set, and if
the querystring is set, the cookie should exist. f not, display a page
saying cookies are required to use your site.

-- bruce (sqlwork.com)

Kelly wrote:

We just switched our web application from .NET 1.1 to 2. Once client can't
login out of several that have been successful. They enter a correct user
name and password, click the login button and they are redirected back to
login with no errors or login failure. The same login account works fine from
other machines at different locations.

This client had no problem logging in before we switched. The login
procedures are essentially the same except for the .NET version. They are
using an updated IE6 browser.

Here is what I'm doing:

Build ticket:
Dim ticket As New FormsAuthentica tionTicket(1, ".TICKETNAM E",
System.DateTime .Now, System.DateTime .Now.AddMinutes (30), False,
Session.Session ID)
Dim authCookie As New HttpCookie(Form sAuthentication .FormsCookieNam e,
FormsAuthentica tion.Encrypt(ti cket)) Response.Cookie s.Add(authCooki e)

Make session variables:
Session("LoginN ame") = prmLoginName.Va lue
Session("DocGUI D") = prmDoc.Value
Session("EmpID" ) = prmEmployeeID.V alue
If prmEmployeeID.V alue 0 Then
Session("UserCl ass") = "Staff"
Else
Session("UserCl ass") = "Client"
End If
Session("GetsCE M") = prmGetsCEMRpt.V alue
Session("GetsPA C") = prmGetsPACRpt.V alue
Session("GetsHO L") = prmGetsHOLRpt.V alue

Check for authentication and session value from the loading page:
If Request.IsAuthe nticated Then
If Session("LoginN ame") <"" Then

[Proceed with page setup routines if successful....]

Else
'Go back and login again
FormsAuthentica tion.SignOut()
Session.Abandon ()
Session.RemoveA ll()

Response.Redire ct(Server_Proto col(Request.Ser verVariables("S ERVER_NAME")) &
"webaccess/login.aspx")
End If

Else

Response.Redire ct(Server_Proto col(Request.Ser verVariables("S ERVER_NAME")) &
"webaccess/login.aspx")
End If

[Patrice]

Looks like a cookie issue. I woudl check the cookie settings. Also do they
have the good datetime, time zone ?

You may want to create a test page to check if cookies seems to work fine...

--
Patrice

"Kelly" <Ke***@discussi ons.microsoft.c oma écrit dans le message de news:
68************* *************** **...icrosof t.com...

>
We just switched our web application from .NET 1.1 to 2. Once client can't
login out of several that have been successful. They enter a correct user
name and password, click the login button and they are redirected back to
login with no errors or login failure. The same login account works fine
from
other machines at different locations.

This client had no problem logging in before we switched. The login
procedures are essentially the same except for the .NET version. They are
using an updated IE6 browser.

Here is what I'm doing:

Build ticket:
Dim ticket As New FormsAuthentica tionTicket(1, ".TICKETNAM E",
System.DateTime .Now, System.DateTime .Now.AddMinutes (30), False,
Session.Session ID)
Dim authCookie As New HttpCookie(Form sAuthentication .FormsCookieNam e,
FormsAuthentica tion.Encrypt(ti cket)) Response.Cookie s.Add(authCooki e)

Make session variables:
Session("LoginN ame") = prmLoginName.Va lue
Session("DocGUI D") = prmDoc.Value
Session("EmpID" ) = prmEmployeeID.V alue
If prmEmployeeID.V alue 0 Then
Session("UserCl ass") = "Staff"
Else
Session("UserCl ass") = "Client"
End If
Session("GetsCE M") = prmGetsCEMRpt.V alue
Session("GetsPA C") = prmGetsPACRpt.V alue
Session("GetsHO L") = prmGetsHOLRpt.V alue

Check for authentication and session value from the loading page:
If Request.IsAuthe nticated Then
If Session("LoginN ame") <"" Then

[Proceed with page setup routines if successful....]

Else
'Go back and login again
FormsAuthentica tion.SignOut()
Session.Abandon ()
Session.RemoveA ll()

Response.Redire ct(Server_Proto col(Request.Ser verVariables("S ERVER_NAME"))
&
"webaccess/login.aspx")
End If

Else

Response.Redire ct(Server_Proto col(Request.Ser verVariables("S ERVER_NAME"))
&
"webaccess/login.aspx")
End If

[=?Utf-8?B?S2VsbHk=?=]

Thanks for the tip. I will set it up. But can you figure why they did not
have trouble with the site before the switch to 2.0?

"bruce barker" wrote:

check if cookies are turned off. you can also detect this problem on the
server by settiing a cookie and redirecting to a page that test if a
cookie exists. say in your redirect add login.aspx?cook ie=set, and if
the querystring is set, the cookie should exist. f not, display a page
saying cookies are required to use your site.

-- bruce (sqlwork.com)

Kelly wrote:

We just switched our web application from .NET 1.1 to 2. Once client can't
login out of several that have been successful. They enter a correct user
name and password, click the login button and they are redirected back to
login with no errors or login failure. The same login account works fine from
other machines at different locations.

This client had no problem logging in before we switched. The login
procedures are essentially the same except for the .NET version. They are
using an updated IE6 browser.

Here is what I'm doing:

Build ticket:
Dim ticket As New FormsAuthentica tionTicket(1, ".TICKETNAM E",
System.DateTime .Now, System.DateTime .Now.AddMinutes (30), False,
Session.Session ID)
Dim authCookie As New HttpCookie(Form sAuthentication .FormsCookieNam e,
FormsAuthentica tion.Encrypt(ti cket)) Response.Cookie s.Add(authCooki e)

Make session variables:
Session("LoginN ame") = prmLoginName.Va lue
Session("DocGUI D") = prmDoc.Value
Session("EmpID" ) = prmEmployeeID.V alue
If prmEmployeeID.V alue 0 Then
Session("UserCl ass") = "Staff"
Else
Session("UserCl ass") = "Client"
End If
Session("GetsCE M") = prmGetsCEMRpt.V alue
Session("GetsPA C") = prmGetsPACRpt.V alue
Session("GetsHO L") = prmGetsHOLRpt.V alue

Check for authentication and session value from the loading page:
If Request.IsAuthe nticated Then
If Session("LoginN ame") <"" Then

[Proceed with page setup routines if successful....]

Else
'Go back and login again
FormsAuthentica tion.SignOut()
Session.Abandon ()
Session.RemoveA ll()

Response.Redire ct(Server_Proto col(Request.Ser verVariables("S ERVER_NAME")) &
"webaccess/login.aspx")
End If

Else

Response.Redire ct(Server_Proto col(Request.Ser verVariables("S ERVER_NAME")) &
"webaccess/login.aspx")
End If

[=?Utf-8?B?S2VsbHk=?=]

Thanks. I will check out cookies and their system date/time. I hadn't thought
of that.

"Patrice" wrote:

Looks like a cookie issue. I woudl check the cookie settings. Also do they
have the good datetime, time zone ?

You may want to create a test page to check if cookies seems to work fine...

--
Patrice

"Kelly" <Ke***@discussi ons.microsoft.c oma écrit dans le message de news:
68************* *************** **...icrosof t.com...

We just switched our web application from .NET 1.1 to 2. Once client can't
login out of several that have been successful. They enter a correct user
name and password, click the login button and they are redirected back to
login with no errors or login failure. The same login account works fine
from
other machines at different locations.

This client had no problem logging in before we switched. The login
procedures are essentially the same except for the .NET version. They are
using an updated IE6 browser.

Here is what I'm doing:

Build ticket:
Dim ticket As New FormsAuthentica tionTicket(1, ".TICKETNAM E",
System.DateTime .Now, System.DateTime .Now.AddMinutes (30), False,
Session.Session ID)
Dim authCookie As New HttpCookie(Form sAuthentication .FormsCookieNam e,
FormsAuthentica tion.Encrypt(ti cket)) Response.Cookie s.Add(authCooki e)

Make session variables:
Session("LoginN ame") = prmLoginName.Va lue
Session("DocGUI D") = prmDoc.Value
Session("EmpID" ) = prmEmployeeID.V alue
If prmEmployeeID.V alue 0 Then
Session("UserCl ass") = "Staff"
Else
Session("UserCl ass") = "Client"
End If
Session("GetsCE M") = prmGetsCEMRpt.V alue
Session("GetsPA C") = prmGetsPACRpt.V alue
Session("GetsHO L") = prmGetsHOLRpt.V alue

Check for authentication and session value from the loading page:
If Request.IsAuthe nticated Then
If Session("LoginN ame") <"" Then

[Proceed with page setup routines if successful....]

Else
'Go back and login again
FormsAuthentica tion.SignOut()
Session.Abandon ()
Session.RemoveA ll()

Response.Redire ct(Server_Proto col(Request.Ser verVariables("S ERVER_NAME"))
&
"webaccess/login.aspx")
End If

Else

Response.Redire ct(Server_Proto col(Request.Ser verVariables("S ERVER_NAME"))
&
"webaccess/login.aspx")
End If