By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,918 Members | 1,912 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,918 IT Pros & Developers. It's quick & easy.

One client can't login to our site

P: n/a

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 FormsAuthenticationTicket(1, ".TICKETNAME",
System.DateTime.Now, System.DateTime.Now.AddMinutes(30), False,
Session.SessionID)
Dim authCookie As New HttpCookie(FormsAuthentication.FormsCookieName,
FormsAuthentication.Encrypt(ticket)) Response.Cookies.Add(authCookie)

Make session variables:
Session("LoginName") = prmLoginName.Value
Session("DocGUID") = prmDoc.Value
Session("EmpID") = prmEmployeeID.Value
If prmEmployeeID.Value 0 Then
Session("UserClass") = "Staff"
Else
Session("UserClass") = "Client"
End If
Session("GetsCEM") = prmGetsCEMRpt.Value
Session("GetsPAC") = prmGetsPACRpt.Value
Session("GetsHOL") = prmGetsHOLRpt.Value

Check for authentication and session value from the loading page:
If Request.IsAuthenticated Then
If Session("LoginName") <"" Then

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

Else
'Go back and login again
FormsAuthentication.SignOut()
Session.Abandon()
Session.RemoveAll()

Response.Redirect(Server_Protocol(Request.ServerVa riables("SERVER_NAME")) &
"webaccess/login.aspx")
End If

Else

Response.Redirect(Server_Protocol(Request.ServerVa riables("SERVER_NAME")) &
"webaccess/login.aspx")
End If
Oct 16 '07 #1
Share this Question
Share on Google+
6 Replies


P: n/a
Would they have the correct framework installed on their computer?

"Kelly" <Ke***@discussions.microsoft.comwrote in message
news:68**********************************@microsof 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 FormsAuthenticationTicket(1, ".TICKETNAME",
System.DateTime.Now, System.DateTime.Now.AddMinutes(30), False,
Session.SessionID)
Dim authCookie As New HttpCookie(FormsAuthentication.FormsCookieName,
FormsAuthentication.Encrypt(ticket)) Response.Cookies.Add(authCookie)

Make session variables:
Session("LoginName") = prmLoginName.Value
Session("DocGUID") = prmDoc.Value
Session("EmpID") = prmEmployeeID.Value
If prmEmployeeID.Value 0 Then
Session("UserClass") = "Staff"
Else
Session("UserClass") = "Client"
End If
Session("GetsCEM") = prmGetsCEMRpt.Value
Session("GetsPAC") = prmGetsPACRpt.Value
Session("GetsHOL") = prmGetsHOLRpt.Value

Check for authentication and session value from the loading page:
If Request.IsAuthenticated Then
If Session("LoginName") <"" Then

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

Else
'Go back and login again
FormsAuthentication.SignOut()
Session.Abandon()
Session.RemoveAll()

Response.Redirect(Server_Protocol(Request.ServerVa riables("SERVER_NAME"))
&
"webaccess/login.aspx")
End If

Else

Response.Redirect(Server_Protocol(Request.ServerVa riables("SERVER_NAME"))
&
"webaccess/login.aspx")
End If

Oct 16 '07 #2

P: n/a
"Rockn" <Ro***@newsgroups.nospamwrote in message
news:ud**************@TK2MSFTNGP05.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

Oct 16 '07 #3

P: n/a
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?cookie=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 FormsAuthenticationTicket(1, ".TICKETNAME",
System.DateTime.Now, System.DateTime.Now.AddMinutes(30), False,
Session.SessionID)
Dim authCookie As New HttpCookie(FormsAuthentication.FormsCookieName,
FormsAuthentication.Encrypt(ticket)) Response.Cookies.Add(authCookie)

Make session variables:
Session("LoginName") = prmLoginName.Value
Session("DocGUID") = prmDoc.Value
Session("EmpID") = prmEmployeeID.Value
If prmEmployeeID.Value 0 Then
Session("UserClass") = "Staff"
Else
Session("UserClass") = "Client"
End If
Session("GetsCEM") = prmGetsCEMRpt.Value
Session("GetsPAC") = prmGetsPACRpt.Value
Session("GetsHOL") = prmGetsHOLRpt.Value

Check for authentication and session value from the loading page:
If Request.IsAuthenticated Then
If Session("LoginName") <"" Then

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

Else
'Go back and login again
FormsAuthentication.SignOut()
Session.Abandon()
Session.RemoveAll()

Response.Redirect(Server_Protocol(Request.ServerVa riables("SERVER_NAME")) &
"webaccess/login.aspx")
End If

Else

Response.Redirect(Server_Protocol(Request.ServerVa riables("SERVER_NAME")) &
"webaccess/login.aspx")
End If
Oct 16 '07 #4

P: n/a
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***@discussions.microsoft.coma écrit dans le message de news:
68**********************************@microsoft.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 FormsAuthenticationTicket(1, ".TICKETNAME",
System.DateTime.Now, System.DateTime.Now.AddMinutes(30), False,
Session.SessionID)
Dim authCookie As New HttpCookie(FormsAuthentication.FormsCookieName,
FormsAuthentication.Encrypt(ticket)) Response.Cookies.Add(authCookie)

Make session variables:
Session("LoginName") = prmLoginName.Value
Session("DocGUID") = prmDoc.Value
Session("EmpID") = prmEmployeeID.Value
If prmEmployeeID.Value 0 Then
Session("UserClass") = "Staff"
Else
Session("UserClass") = "Client"
End If
Session("GetsCEM") = prmGetsCEMRpt.Value
Session("GetsPAC") = prmGetsPACRpt.Value
Session("GetsHOL") = prmGetsHOLRpt.Value

Check for authentication and session value from the loading page:
If Request.IsAuthenticated Then
If Session("LoginName") <"" Then

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

Else
'Go back and login again
FormsAuthentication.SignOut()
Session.Abandon()
Session.RemoveAll()

Response.Redirect(Server_Protocol(Request.ServerVa riables("SERVER_NAME"))
&
"webaccess/login.aspx")
End If

Else

Response.Redirect(Server_Protocol(Request.ServerVa riables("SERVER_NAME"))
&
"webaccess/login.aspx")
End If

Oct 16 '07 #5

P: n/a
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?cookie=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 FormsAuthenticationTicket(1, ".TICKETNAME",
System.DateTime.Now, System.DateTime.Now.AddMinutes(30), False,
Session.SessionID)
Dim authCookie As New HttpCookie(FormsAuthentication.FormsCookieName,
FormsAuthentication.Encrypt(ticket)) Response.Cookies.Add(authCookie)

Make session variables:
Session("LoginName") = prmLoginName.Value
Session("DocGUID") = prmDoc.Value
Session("EmpID") = prmEmployeeID.Value
If prmEmployeeID.Value 0 Then
Session("UserClass") = "Staff"
Else
Session("UserClass") = "Client"
End If
Session("GetsCEM") = prmGetsCEMRpt.Value
Session("GetsPAC") = prmGetsPACRpt.Value
Session("GetsHOL") = prmGetsHOLRpt.Value

Check for authentication and session value from the loading page:
If Request.IsAuthenticated Then
If Session("LoginName") <"" Then

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

Else
'Go back and login again
FormsAuthentication.SignOut()
Session.Abandon()
Session.RemoveAll()

Response.Redirect(Server_Protocol(Request.ServerVa riables("SERVER_NAME")) &
"webaccess/login.aspx")
End If

Else

Response.Redirect(Server_Protocol(Request.ServerVa riables("SERVER_NAME")) &
"webaccess/login.aspx")
End If
Oct 16 '07 #6

P: n/a
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***@discussions.microsoft.coma écrit dans le message de news:
68**********************************@microsoft.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 FormsAuthenticationTicket(1, ".TICKETNAME",
System.DateTime.Now, System.DateTime.Now.AddMinutes(30), False,
Session.SessionID)
Dim authCookie As New HttpCookie(FormsAuthentication.FormsCookieName,
FormsAuthentication.Encrypt(ticket)) Response.Cookies.Add(authCookie)

Make session variables:
Session("LoginName") = prmLoginName.Value
Session("DocGUID") = prmDoc.Value
Session("EmpID") = prmEmployeeID.Value
If prmEmployeeID.Value 0 Then
Session("UserClass") = "Staff"
Else
Session("UserClass") = "Client"
End If
Session("GetsCEM") = prmGetsCEMRpt.Value
Session("GetsPAC") = prmGetsPACRpt.Value
Session("GetsHOL") = prmGetsHOLRpt.Value

Check for authentication and session value from the loading page:
If Request.IsAuthenticated Then
If Session("LoginName") <"" Then

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

Else
'Go back and login again
FormsAuthentication.SignOut()
Session.Abandon()
Session.RemoveAll()

Response.Redirect(Server_Protocol(Request.ServerVa riables("SERVER_NAME"))
&
"webaccess/login.aspx")
End If

Else

Response.Redirect(Server_Protocol(Request.ServerVa riables("SERVER_NAME"))
&
"webaccess/login.aspx")
End If


Oct 16 '07 #7

This discussion thread is closed

Replies have been disabled for this discussion.