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 6 2264
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
"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
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
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
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
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
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: lionking |
last post by:
oracle 9.2 on redhat 7.3
I can't login as system/password as sysdba to dbastudio (I started it by
typing oemapp dbastudio).
I can login as normal though... what might be the problem?
|
by: Dale Jhonson |
last post by:
Client area and login
new to Mysql, I would like to store pictures in mysql and have
differnt customer accessing them through password. Is there some ready
made solutions or tools that make the...
|
by: Sarah Haff |
last post by:
Hello All,
Is it possible to have alternating color font for DropDown/List box in
html?
I have an FatClient application written in C, and I am trying to
webify it. The application uses...
|
by: AG |
last post by:
Every night i want to send the new records that are created from my
remote client to my FTP site, using a application which sets up an
internet connection on the client , exports the data to the...
|
by: ad |
last post by:
I use Login control's Authenticate event to authenticate use.
I find that different users can use the same ID to login in the same time.
How can I restrict that the some ID can only login once in...
|
by: active |
last post by:
Using VS2005 I created a web site which I can view on my machine.
I want to show it to someone that doesn't have VS2005 on his machine.
Is there some way I can put the site on a CD and view it...
|
by: mattsql22 |
last post by:
I just installed Red Hat Enterprise 5, along with MySQL. I have run mysql_install_db and I can see the mysql folder that contains the 'mysql' database with the users. Unfortunately, I can't login...
|
by: JRough |
last post by:
I cannot log into our web site. I have a test web site and a real
site. On Friday I could log in and today Monday I cannot log in. I
have 2 databases In PHPMyAdmin, the real database and and a...
|
by: kavuris |
last post by:
I Installed windows server 2003 in IBM Server 3400 and 100 workstations are using that server. My problem I can not login to server while gving appropriate user name and password, after l;oggin...
|
by: isladogs |
last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM).
In this month's session, we are pleased to welcome back...
|
by: Vimpel783 |
last post by:
Hello!
Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
|
by: jfyes |
last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
|
by: ArrayDB |
last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
|
by: PapaRatzi |
last post by:
Hello,
I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
|
by: CloudSolutions |
last post by:
Introduction:
For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
|
by: af34tf |
last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you
|
by: Faith0G |
last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome former...
| |