+1 for this.
I often have to switch browsers on my tablet, unless I want to clear the whole browser history.
On a desktop I can selectively clear cookies for sas.com, at least in PaleMoon.
Thanks for this feedback -- I'll check with our IT folks to see what might be going on.
I also saw it a couple of times during the weekend (from a home machine), but chalked it up to weekend work. When I refreshed I was logged in, no problem. Now that I see others are seeing issues, I'll pursue it.
I saw that error earlier this week too (Sunday or Monday I think) and had to switch to a different browser to login. I used to get that error quite regularly just after communities switched over from Jive to Lithium, but haven't seen it for a while now.
I've raised this issue with our IT group and they are investigating. Like many tech problems, this is difficult to replicate. However, the good news is that I've seen the same problem from home (but not at work). I've been able to capture some network logs for the team.
You're not supposed to see the HTTP 500 error, but your SAS profile login (used for communities) can "expire" after 7 days (assuming you selected the "keep me logged in" option). The state is tracked using cookies. When your login cookie expires, you should see the user/pw challenge for SAS profile.
Normal tech support advice is "delete all of your cookies". I like to take a more surgical approach.
In Chrome, you can find just your SAS-related cookies:
Firefox is a little different:
Hopefully this is a one-time action on your part. But we'll continue to look into it from our side.
The problem comes with the browsers of mobile devices. These often don't have the granularity in deleting the browser history that you get on desktops. You can only remove everything, including all data from other websites.
Normal tech support advice is "delete all of your cookies".
Can't they just make it smart enough to re-direct to the login page and re-create the cookie when it is expired?
I find that if I close all browser windows and then try again it will successfully go to the logon page. I find that much easier than trying to locate the cookie to delete.
@Tom, yes, that's the design -- it is supposed to be smart enough to renew your login (prompting you to sign in as needed). But since that's sometimes not working, I offered the "delete cookie" approach as a temp fix for people who see this chronically. In the meantime, our IT staff is looking into it.
Registration is open! SAS is returning to Vegas for an AI and analytics experience like no other! Whether you're an executive, manager, end user or SAS partner, SAS Innovate is designed for everyone on your team. Register for just $495 by 12/31/2023.
If you are interested in speaking, there is still time to submit a session idea. More details are posted on the website.