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!
Related
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.
We are unable to publish the LUIS application. Publish button was disabled. Please find the attached screenshot and suggest on this please.
I have this problem in the afternoons (UK) - wait a few hours and it's fine. I wonder if the system gets overloaded at times.
The reason was session time out. I looked at console and found 400 error which says token is missing. So i signed out and signed back in. It started working. I was able to publish code to any slot specified.
It looks like a bug and microsoft should address this session timeout with auto redirect or a proper message.
Try Browsing/Publishing in Incognito mode / Private Browsing.
There are Caching related issue in luis portal
Every day at about 18:30 GMT we get lots of timeouts and 503 and publishing problems. We decided not to publish during that time.
Today we got more delays than usual
https://azure.microsoft.com/en-us/status/ show no errors in westus (the endpoint we are reaching)
It'd very nice to get a LUIS Status page (and not the global Cognitive Status)
This bug has been around for a while now. Advice from Microsoft support was to:
delete all cookies for luis.ai
sign out of the session
then sign back
in
When you sign in again the publish to production button should be enabled again
This is a weird problem and I apologize beforehand that I may not give enough details:
We have a pretty standard Angular app that needs to access an API on a different (sub-)domain, using CORS. Everything works perfectly fine on Chrome and Firefox. We also got it working on IE >=9.
Unfortunately, some of our customers need to access our public website from within their company intranet. In this case, using IE, only a couple API requests go through. Chrome and Firefox cause no problems.
They can create a sessionThey get the result of a second GET requestBut the third request fails
In the console, we see an Access Denied message caused by a GET request.
**AND**: When they reload the page, the third request goes through. One customer could bypass his intranet and access our website directly. Then, everything worked like a charm.
Please note that we are only aware of issues with IE 11.
Any help is really appreciated.
I have a VM that I set up to do development on two sites hosted on Acquia with the same codebase. I'm using version Drupal 7.26. I have it where I can access both sites from the host computer, but when I try to log in using /user/login on either site, I get nothing. The POST returns a 404 containing the log in page again.
I've tried settings $cookie_domain = '.my-site.dev' as well as $cookie = 'www.mysite.dev'. Neither has any effect. I also tried adding a bunch of random charactersto the file to make sure I was editing the correct file; with the random characters, pages didn't load at all. (See https://www.drupal.org/node/611920#comment-3110010.)
I also tried doing repair table sessions. I forgot which site I saw that recommendation from. I also tried delete from sessions just for kicks. Neither worked.
Any ideas? Thanks!
edit: Per https://www.drupal.org/node/261411#comment-3182566, I tried to go to www.mysite.dev/?q=user/login. This did not give me a 404, but I had tried (unsuccessfully, it seems) to reset my password through the database. I'm at least getting an error about a bad username/password combination rather than nothing at all. Still, I would think /user/login should have worked, too.
edit 2: The production site uses CAS, but logging in through /user/login still works.
I have a CakePHP website that's been working great.
I just developed a new functionality that at one point auto-logs the user in, and redirects him to a page that's behind the login wall.
This works perfectly well in my dev machine, but in production, the user gets redirected to the login page.
Relevant code: (not much)
$objCustomer = $this->Customer->findById($customerId);
$this->Auth->login($objCustomer);
$this->redirect("/customers/signup");
Customer is the Model that's used for authentication.
In the server, I see that I AM getting redirected to /customers/signup, and that redirects me to /customers/login
The thing that confuses me the most is that this works perfectly in my machine.
I dumped the return value of Auth->Login in the server, and it returns 1, so in theory everything is fine and the user should've been logged in.
Some things I can think of that are different between my machine and the server:
Dev machine is Windows, Server is Linux. This sometimes introduces case-sensitivity issues, but the signup method i'm redirecting to is all lowercase, I don't see where there could be such a problem here.
Dev machine is IIS, Server is LiteSpeed. Maybe Litespeed is screwing with something? This would be the first time in over a year running this site in production that i'd find something different because of LiteSpeed
Production site is over SSL, dev is not. I don't see how this could be a problem.
Any ideas are infinitely welcome!
Thank you!
I had problems too with authentication working fine on my machine in development mode, but not working on the server in production mode. Surprisingly, when I changed the server to development mode it started working correctly. Then I changed back to production, and it was still working. Perhaps it was some cache issue.
After a LOOOONG process of trying different weird things, it turns out it all boils down to this:
ini_set('session.referer_check', $this->host);
That's part of CakePHP's standard security features... It sets that INI setting.
If the request made to the action that'll call Auth->login is coming from another host (domain/subdomain/whatever), PHP will consider the session invalid, which effectively kills the auto-login attempt.