Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / October 2007

Tip: Looking for answers? Try searching our database.

One client can't login to our site

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Kelly - 16 Oct 2007 12:35 GMT
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.ServerVariables("SERVER_NAME")) &
"webaccess/login.aspx")
           End If

       Else
           
Response.Redirect(Server_Protocol(Request.ServerVariables("SERVER_NAME")) &
"webaccess/login.aspx")
       End If
Rockn - 16 Oct 2007 14:35 GMT
Would they have the correct framework installed on their computer?

> 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
[quoted text clipped - 52 lines]
> "webaccess/login.aspx")
>        End If
Mark Rae [MVP] - 16 Oct 2007 14:46 GMT
> 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...

Signature

Mark Rae
ASP.NET MVP
http://www.markrae.net

bruce barker - 16 Oct 2007 16:25 GMT
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)

> 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
[quoted text clipped - 49 lines]
> "webaccess/login.aspx")
>         End If
Kelly - 16 Oct 2007 19:29 GMT
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?

> 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
[quoted text clipped - 57 lines]
> > "webaccess/login.aspx")
> >         End If
Patrice - 16 Oct 2007 17:37 GMT
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

> 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
[quoted text clipped - 52 lines]
> "webaccess/login.aspx")
>        End If
Kelly - 16 Oct 2007 19:31 GMT
Thanks. I will check out cookies and their system date/time. I hadn't thought
of that.

> Looks like a cookie issue. I woudl check the cookie settings. Also do they
> have the good datetime, time zone ?
[quoted text clipped - 60 lines]
> > "webaccess/login.aspx")
> >        End If

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.