Hey Guys,

 I'm new around and I thought this is probably the best place to help me solve my dilemma, I am developing a website for almost a year now and the login control was implemented a logn time ago, however all of a sudden it will not authenticate on Internet Explorer 7 when the application is published, it doesn't even provide a message that authentication was unseccssful or throws any error, it just refreshes the same page. however this problem doesn't occure when I try the same website on FireFox 2.0...Also when I run the page locally on Cassini it work great on both browsers...This is one of the weirdest errors I have ever faced. what could have gone wrong on the server side to cause this? knowing nothing changed on the server-side...I'll provide a snapshot of the login control below

<asp:Login ID="LoginControl" runat="server" BackColor="Transparent" BorderColor="Transparent" BorderPadding="4" BorderWidth="0px" Font-Names="Verdana" Font-Size="Small" ForeColor="Transparent" CreateUserUrl="basicregistration.aspx" DestinationPageUrl="index.aspx" CreateUserText="Register in Tripbot" PasswordRecoveryText="Forgot your password?" PasswordRecoveryUrl="forgotpassword.aspx" TitleText="SignIn" RememberMeSet="True" TextLayout="TextOnTop" Height="193px">

<LayoutTemplate>

<table cellpadding="0" cellspacing="0" style="width:100%">

<tr>

<td align="right" style="width: 100px; text-align: left;">

<asp:Label ID="UserNameLabel" runat="server" AssociatedControlID="UserName" Width="100px" CssClass="whitemedium">Email</asp:Label></td>

<td style="TEXT-ALIGN: left; width:200px">

<asp:TextBox ID="UserName" runat="server" Font-Size="0.8em" Width="200px"></asp:TextBox><asp:RequiredFieldValidator ID="UserNameRequired" runat="server" ControlToValidate="UserName" ErrorMessage="User Name is required." ToolTip="User Name is required." ValidationGroup="LoginControl">*</asp:RequiredFieldValidator>

</td>

</tr>

<tr>

<td align="right" style="width: 100px; text-align: left;">

<asp:Label ID="PasswordLabel" runat="server" AssociatedControlID="Password" Width="100px" CssClass="whitemedium">Password</asp:Label></td>

<td style="TEXT-ALIGN: left">

<asp:TextBox ID="Password" runat="server" Font-Size="0.8em" TextMode="Password" Width="200px"></asp:TextBox><asp:RequiredFieldValidator ID="PasswordRequired" runat="server" ControlToValidate="Password"

ErrorMessage="Password is required." ToolTip="Password is required." ValidationGroup="LoginControl">*</asp:RequiredFieldValidator></td>

</tr>

<tr>

<td></td>

<td align="left">

<asp:ImageButton ID="LoginButton" runat="server" CommandName="Login" ImageUrl="~/Images/newui/loginbutton.gif" ValidationGroup="LoginControl" />

</td>

</tr>

<tr>

<td colspan="2" style="text-align: left">

<asp:CheckBox ID="RememberMe" runat="server" Text="Remember me" CssClass="whitemedium" />

<asp:LinkButton ID="btnForgetMe" runat="server" Font-Size="Small" OnClick="btnForgetMe_Click">Forget Me</asp:LinkButton></td>

</tr>

<tr>

<td align="center" colspan="2" style="color: red; text-align: left;">

<asp:Literal ID="FailureText" runat="server" EnableViewState="False"></asp:Literal>

</td>

</tr>

</table>

</LayoutTemplate>

</asp:Login>

 I handle the login functio manually and it was working great and no one really changed anything about it.

 

Thx in advance

 

1) Does this happen for all your IE7 users?

2) Are you using persitent form authentication tickets?

3) In your <from element in web.config, add the following:

cookieless="autodetect" or "useruri" and let us know if that helps.

 

Thanks

/kadji

Hey Kadji, Thank you for your help, to answer your questions

1) Does this happen for all your IE7 users?

Yes, but only when the site is being accessed from the server (IIS vs. Cassini) if it's run on the local machine it works just fine.

2) Are you using persitent form authentication tickets?

Yes, and it was perfectly working before.

3) In your <from element in web.config, add the following:

cookieless="autodetect" or "useruri" and let us know if that helps.

I tried both and the problem is still there...what kind of configuration change can cause this as I really see no reason for this to happen.

Thank you again,

Ray 

 

I tried this today on local IIS and it worked great, I also tried it on server network IIS and it also worked great. When I trace the authentication code everything is in order and all functions are executed properly...however the authentication ticket is missing...

Ray

I checked and it seems the createpersistent flag in setauthcookie/redirectfromloginurl is causing this problem when it's set to true...I couldn't really understand why but setting this to false would solve the problem...

 

talkin about weird :)

Does the login control not work in IE (Internet Explorer 6 , 7 , any) and works fine in Firefox (1.0 , 2.0 , any )?

    The problem always occurs after publishing, right?, not during development  (unless you've incorporated Google AdSense in the development version also).  The culprit is Google AdSense people.

A simple test : Use the visual studio comment toolbutton to comment out all the google scripts you've incorporated into your site, and check if login control works .....

    I have created a custom user control that contains the javascript from google and am registering and using the usercontrol wherever i need the Advertisement.  So i commented out all the Ad usercontrols i used in the login page AND the master page that login.aspx uses, so that in the final rendered version, google's scripts don't come with login control's rendered code at all. Now the login control works fine. Then i included Googles AdSense Scripts , uncommenting google script usercontrols and tried , the problem was back.

    People think master pages are the reason login fails in IE-not-Firefox, but, no, the google ads mostly invariably placed in master pages are the real reason. Also not only does the login control cause problems in IE and not in Firefox, but also the LoginStatus control and a few other controls also cause problems in IE and not in Firefox. Some blogs & comments say authorization cookie is not picked up by the browser , i think that may be true , becoz google adsense scripts do some authentication cookie work themselves . The script downloaded from google by the stubs we put in our Aspx pages are probably the reason. I tried going through it , but could'nt make head or tail of it... way too complex for me.

Both the login & loginstatus controls work fine in firefox alonside google ads & scripts , though sometimes i see wierd behaviour ... if I clear all cookies & temp. internet files in firefox, the first time i click on the login button, nothing happens but a refresh. The second time i click it , it login fine.(All of this alongside google adscripts) . Justification :

• Google must have different scripts for IE and Firefox - which could be the reason IE can't perform correct while using ASP.NET 2.0 Login Controls , while firefox can.
• Or Login Control Library renders differently based on the browser (i don't know) the login page is often the first page requested by the client , in which case the asp runtime can see the user agent string and render accordingly....
  
• Google and ASP.NET may produce the same code for both browsers in which case , the browser architecture is responsible for this unique behaviour. (means Firefox is good!)
• Some folks think remember me check box - may be the cause, it defenitely could becoz it (leaves) involves a cookie, which i think is what(the cookies) google script wrecks !
• Most blogs and forums(especially in aspblog  aspforum expertsexchange webdeveloper) say : Login control is suddenly broken - means it was working fine previously... they just don't connect the point of time the problem was discovered was always after a short or long time AFTER hooking up google ads ... for me i took i long time discovering the error after setting up google adsense , so it didnt occur to me adsense could be the change that causes the problem.
• We all use  different kinds of AdSense units  : so the problem also differs slightly : to some the pressing of login button does nothing but refresh the page, to me there was no reaction at all after i pressed the login button after entering correct & wrong pair of username and password , to some it seems there is redirect & error code 404 is returned once they click on the login button.

Best Workaround :

1. Create another similar master page without the ads , and use this as master for login.aspx - you preserve the same look and feel, but forgo ads till Microsoft or Google comes up with a solution.
2. Enclose all ads between <% if(!Page.title.equals("Login")){ %>    and    <%} %>, which means u've solved the Login Control , but still the LoginStatus and other login controls could still give you a problem.(make sure you title the login page to "Login")
3. In case you are'nt using a master page at all for login.aspx , new login page without the ads , must be built.

Go Here for more Info : http://www.thiagarajan.net/ZaszBlog/post/2008/05/Login-control-ASPNET-works-in-Firefox-but-not-in-IE.aspx

 

 

 

 

I had the same problem too, took out the Master Pages, have no adverts and still the Login would work with Firefox but not IE......

Managed to find a solution after a while:

In Internet Explorer, go to Tools-->Internet Options-->Privacy-->Tick OVERRIDE AUTOMATIC COOKIE HANDLING-->Accept or Prompt First-party Cookies, Accept or Prompt Third-party Cookies. You may need to configure/switch off ZoneAlarm too

HTH

Tushar
 

Four years down the track, I'm working on a site that is almost ready to go live, make some minor changes to my main master page and...  I can no longer log in, either with IE7 or Firefox.  No errors, no messages, nothing, just bumps me back to the login page.

No Google Ads, tried everything else mentioned here, nada..

:-(

Ok, after a little bit more experimentation, I have discovered that if I place my loginstatus control *above* the contentplaceholder (as in the flow of the html), the login stops working - anywhere below it, and it starts working again.

 

Guess I'll just have to find somewhere else it stick it...

 

Rob

This is a realy strange issue. In my case, I'm using WebParts along with the Membership API stuff, that's all baked in .NET, along with the LoginStatus control, and the LoginStatus control generates a postback, but stays on the current page instead of redirecting to the Login.aspx page. I have tried everything suggested on this forum to no avail.

By the way, I'm using ASP.NET 3.5 with Visual Studio 2008. Every thing was working fine, then all of a sudden it wont work (it's broke in both IE7 and FireFox 3).

Also, I just found out that when I navigate to the login page manually, and try to login, it doesn't work. The whole Membership/Authentication API seems to be broken!!

Has anyone figured out a solution to this?

It appears I had the following rogue line of code in my Page_Load handler of my MasterPage:

this.WebPartManager1.Personalization.ToggleScope();

Removing that line fixed the issue. The issue was I wasn't checking if WebPartManager1.Personalization.CanEnterSharedScope was True before calling the ToggleScope method.

I don't know if this'll help anyone else, but it fixed my issue.

 Hi,

I have the very same problem......... did you finally find what the problem was ?

please let me know ..........

In Internet Explorer, go to Tools-->Internet Options-->Privacy-->Tick OVERRIDE AUTOMATIC COOKIE HANDLING-->Accept or Prompt First-party Cookies, Accept or Prompt Third-party Cookies. You may need to configure/switch off ZoneAlarm too