Project Overview:
I have made a Web System by using Django+AngularJS.
The Web System is basically an Authentication Portal, User logs in and does the stuff etc.
Problem Statement:
The problem I am facing is that I have logged out my system successfully and closed the browser. Then I visit the Web Page after a week, when I opened the Link https://www.foo.xyz so normally Login Page should Appear but instead of that it directs me to the Home of the System, which is not normal.
And it keeps happening until and I cleared the Browser's Cache, Restarted the Browser and Reopened the link.
(I used Chrome and Firefox and I am facing the issue in both of them.)
What I need:
First, thing is that I don't why does this happen?
Second, how can I fix it permanently?
As I don't know how you made your web system, I'm going to be assuming a few things here.
Your page keeps the authentication information in cache, so that's why the page goes to the home and doesn't once the cache is deleted. If you want this not to happen, you're gonna need to find some way to auto-remove the authentication from the cache after x amount of time.
Related
We have an embedded microApp that is setup on a thirdparty website (Saba) that is designed to pass a session token to our Application. We are initiating a User login by presenting them an embedded browser session using WebView2 in our wpf application. Then after a successful login the microApp on the Saba homepage passes back a session token. This appears to be where the application is hanging, waiting for the valid session token to be returned.
This had been working great up until the last 24 hrs, when we are experience hangs on logging in. It appears that trying to access webview via the console/inspector from Edge doesn't work either. "window.chrome.webview" shows undefined.
We are actively scouring any reference we can find to see if there is information about webview support being deprecated or moved but we haven't yet. If anyone has any ideas or resources of where we may be able to find some answer that would be much appreciated.
DNN site taking more time to load landing page for the first time.
As you did not provide a lot of information about your problem (Which DNN/IIS/Windows version?) I can only guess what you really mean. But most propably it is the behaviour of the IIS AppPool that shuts down after a while when no one visits the site or the server has been restarted or the AppPool is recycled.
I wrote a blog post a while ago how to fix it, but that was for IIS 7 (and before), please read also the comments which point out a more accurate way to get rid of this problem since IIS 8.
I created a ASP.NET single page application. When I run it I get the following 404.15 error. I see the same error with an MVC application without a Web API in it also.
I commented out the ConfigureAuth code as below:
public partial class Startup
{
public void Configuration(IAppBuilder app)
{
//ConfigureAuth(app);
}
}
Now I get another error which is below:
I tried to duplicate this on a different laptop, and I don't see a problem there.
Is this a directory level permission issue on this particular laptop where I created the app? Appreciate anyone can shed some light on this to fix this.
UPDATE 11/9/2014
I did some further debugging and found that the applications works fine with no authentication and Windows Authentication. When the authentication is forms, I see this problem happening. As you see in the IntelliTrace, the GET request is looping back to Account/Login multiple times and finally give with a 404.15 error. I added a authorization section in the web.config to allow all users to access the resources with , I still see the errors.
I see a major difference between how my laptop and the surface pro 2 behaving with the same application. In my surface pro 2, the home page is displayed and the redirect to account/login never happens. But in the laptop the redirection is happening to account/login.
There are tables in the surface pro 2 created by the asp.net identity. But in my laptop there are no tables. I believe when the application starts, there is no requirement for the tables and the control should go to the home page.
I hope anyone can provide an answer with my additional info.
At first sight looking at the requestedUrl it may be the case that you are always redirecting to the same page (the login page) which creates an infinite redirect loop until the request url becomes too long: Since there is no code I can't be sure about it but I would suggest you to check your redirect url. The authentication appears just because you outcommented the ConfigureAuth method but I don't think it will solve the problem.
I'm stumped. We have a client who cannot log in to our system and yet we can log in fine using her credentials. She can also log in fine from her friends home.
Upon entering her credentials the screen simply refreshes and nothing happens when in fact she should be brought to a dashboard page. When I monitor the request via the Chrome web developer tools I can see that the dashboard does get requested after log in but then suddenly we're brought back to the log in page.
Now I've cleared her cache, cookies and all other temporary internet files from both IE9 (her default browser) and Chrome. Nothing happens. I've read that changing session names might help but that did nothing either.
The system is using the newest version of CakePHP (2.2.1) and absolutely any help would be appreciated.
This issue has been solved. Turns out this client in particular had the wrong date and time set on her computer. Upon setting the correct date and time, she has been able to log in absolutely fine since.
Thanks everyone for help!
I'm implementing LiveID authentication on my website. I've done it before, but not on this particular platform, MojoPortal.
The sign-in works properly, but when I attempt to sign-out, I get the error message quoted below. My browser is not blocking cookies.
I get the same message when logging in to and out of, say, MSDN with a LiveID too now. I can't figure out if there's something about my site's programming that is interfering with the sign-out process of LiveID (since I believe that all (recent?) websites get sent a sign-out command) OR if live.com is just having issues lately and this is a coincidence.
Couldn't sign you out
We couldn't sign you out because your
browser is blocking cookies. To sign
out, close all of your browser
windows.
To keep this from happening again,
change your browser's settings to
allow cookies. If you don't know how
to do that, see your browser's help.
AFAICT if you block third party cookies — a not uncommon practice — then the Windows Live sign out routine presents a false alarm about signing out. In this situation the advice —
close all of your browser windows
— may be ignored. If you simply proceed to a page that requires a Windows Live ID, the prompt to sign in will appear.
Screen shots at http://www.wuala.com/grahamperrin/public/2010/09/27/a are from Chromium 6.0.443.0 (50323) after clearing all browsing data. I also tested Safari 5.0.2 in Mac OS X 10.6.x and again, found that the false alarm occurs only when third party cookies are blocked.
No mention of third party cookies at any of the following —
Haven't been able to sign out
When I try to close my hotmail, this is what I get: Couldn't sign you out We couldn't sign you out because your browser is blocking cookies. To sign out, close all of your browser windows. …
logout problem - says Couldn't sign you out We couldn't sign you out because your browser is blocking cookies. To sign out, close all of your browser windows. To keep this from happening again, change your browser's settings to allow cookies. If you don't know how to do that, see your browser's help. BUT COOKIES ARE ENABLED OR ELSE I COULDN'T HAVE SIGNED IN! (who can blame them for shouting? ;-)
When signing out of Hotmail I am not being signed out of Windows Live Storage. Refer to displayed messages in the "Add details" section
— so I could be wrong …
This looks like a configuration problem with the rpsserver.xml in your machine
Purge the browser's cookie cache. I seem to recall this error can come up if a corrupted cookie gets written to the local cache.