Security :: Login Control - Remember Me Code No Longer Works
Jan 15, 2011
This code worked until I published a recent set of changes to the web site. It's very strange behavior that I am having trouble debugging. Basically, I implemented some custom code to allow custom configuration of login timeouts from an app settings variable.
When debugging the application, if I click remember me or not, Login works perfectly. Once I post the updated code to the live server, login only works if I have the Remember Me option unchecked. If I check remember me, it does not log in, and it cycles the user back to the default web page. If I access the site from IE on the live server, remember me works correctly.
In order to make the button's click event fire when the text box is highlighted, we have to have a second text box be a part of the form. Make it invisible so that the user never knows it's there. From what research I did, this appears to be an IE-specific problem. Nevertheless, this was the only "solution" I found.
I have two application (one of this is mojo portal): [URL] for some users when they login into "app" then the login in "mojo" doesn't work and viceversa. I've set the machinekey into web.config file. When the users remove all cookies and session data the login works again. The two application are into a Web Farm. Should be ARR the problem?
I'm trying to test the login control without writing any code. According to Murachs book, you can drag and drop the login control onto a Login.aspx form. Use the ASP Configuration Security tool to create user, roles, and access rules for the website. And you should then be prompted for authentication. I created two folders in my website, admin and users. The admin folder has a admin.aspx form and the users folder has a users.aspx form. I also edited the access rules to only allow admin to access the admin.aspx and only allow user to access the users.aspx form.
I've created a new website using forms authentication. Everything works fine on my local DEV machine - I can log in with no problem in any browser.
But as soon as I deploy this to my production server, I am unable to login using IE. I get to the login page and when I click to login, it just reloads that page and never authenticates me. If I use Google Chrome, I can log in without any problems.
I know this sounds similar to the common problem where you don't have your applicationName specified in the web.config file, but I have that specified in all of my providers.
I've tried this in both IE8 and IE9 while adjusting the cookie settings to accept everything and it makes no difference. I've also tried on multiple computers.
Since I can get it to work in Chrome, I feel like there must be a setting in the code somewhere that affects IE differently. I have a hard time believing it's a setting in IE because I use the standard, default setup there.
The only way I could get this close to working was to adjust this forms authentication setting: cookieless = "UseUri". When I did this, I could get past the login screen to my default page, but then when I tried to navigate to any other pages, it would always take me back to the login page and make me login again. It would take me to the requested page each time, but I would still have to login again at every new page request.
Here are a couple of snippets from my web.config file.
I have a issue, when I checked the "remember me" check box when login, but login is doesnt worked. If i unchecked the "remember me", the login function just working fine. It's weird, because this only happen in my production server, it's working fine in my local mechine.
I have a simple login screen that now has to receive its parameters from another web site. I am not sure what we have to do. The other web site, will get the user id and password. the person there is asking me, does he just redirect user tohttp://reports.ourwebsite.com:90/login.aspx?username=Bill&password=testthis is the codes: First is Login.aspx<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Login.aspx.cs" Inherits="Reports.Login" %><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> xmlns="http://www.w3.org/1999/xhtml"
I have an ASP.net application hosted on Win2003 server. When I set the Authenticated Access to just Integrated Windows Authentication, IE7 & IE8 started failing in loging into the site with an error 401.1 ("You are not authorized to view this page"). But Firefox has no issues in loging into the site. why IE is failing to login with Integrated Windows Authentication where FireFox works perfectly?
In login control of asp.net there is a remember me checkbox. What is the functionality of this checkbox? What it does basically? Is there any way to put space between checkbox and its associated label?
I saw Windows Live login control has an extra checkbox Remember my password? How can we achieve this feature in our custom login control? I have read many tutorials but I can not able to solve my queries.
To start, I am a new web developer. I have been writing C# for about a year, but just recently learning web development. I wrote an application that connects to a MySql database and when I run it on my localhost it wokrs great! I created a ubuntu server on amazon ec2 and it is hosting my MySql server. It is up and running just fine. I created a windows 2008 server instance on amazon ec2 to host my asp.net project. I published my project to my windows server and I went to my public IP address and my site was there! it was so easy...
However, when I went to login, I recieved this error: Could not load file or assembly 'MySql.Data, Version=18.104.22.168, Culture=neutral, PublicKeyToken=c5687fc88969c44d' or one of its dependencies. The system cannot find the file specified. I made sure the correct connector was installed on ym server. I have the most recent mysql connector installed. I do not know how the publish actually works. I saw some forum posts that said maybe I was missing DLLs from my bin directory but I cannot even find my bin directory for my project on the server. I also saw some posts about changing the web config file, but that was gibberish to me at this level.
I'm using what I believe is a pretty common/boring/generic implementation of a ModalPopupExtender. I'm using client-side JS to show the dialog when the user clicks a link, and hide it if they click "cancel". I only do a postback if they truly want to save the data.
I can click the link to show the dialog, then click the cancel button to hide it, then click the link to show it... ad infinitum. If I decide to save the data via a postback, everything works well, and the dialog is hidden as a result of the postback, all as expected.
However, once the postback completes, my client-side JS show() never works again. Any attempts to click the link fail quietly; no error messages, the dialog just never shows again.
i have a login, and wanted to know how i could use the remember me function, (so each time the user visits the site, even though they are not logged in, it would auto log them in) but without using the actual remember me checkbox. Is there any extra code i need to write, and if so, what?
im having a login control in my website with a remember me option. i check the remember me but it does not remember me. here is a part of my web.config. i browsed over the other answers on this forum but nothing :( I also have the cookies allowed
my problem is when i close the tab in browser consisting of my application it logs off therefore i want to know that even after closing the browser it should not log off till i press logout button ,as many application provide the same functionality like facebook or even aspforums.net
I am doing a simple secured site using the login control. I would like users to be redirected to their dashboard page once they log in, but after that if they choose to browse I do NOT want them redirected based on their login status. I am using the generic template provided in VWD with the basic login setup in the template including the tabbed ASP menu control - nothing fancy, nothing custom. This is intended to be something very simple and quick. Here is the code I am using for the page load...
So if I do this code WITHOUT the "IsPostBack", logged in users are always redirected to their dashboard and cannot see the hompage. However with that IsPostBack test, the redirect after initial login doesn't work.
I know this is extremely basic and simple, but I am restarting with this stuff after a year away, and I need a nudge.
While i was using asp.net2.0 login control on IIS6.0 (WINDOWS SERVER2003) ON INTRANET FOR Login it shows login failed even it was working right on asp.net development server. i was using asp.net membership provider for this