Closed sot232 closed 5 years ago
Yeah, CAS had some issues today. In such a situation, there's absolutely nothing that can be done in a browser plugin like this. Or a server-based plugin for that matter. If the "Central Authentication System" is broken, then by definition Authentication isn't working.
I am sorry if my question wasn't clear.
I know I can't do a whole lot when CAS is broken. But I was able to access CAS on incognito mode even though I couldn't access the same thing on a normal browser. To me, it seems like somewhere on your side stores my broken call and blocks accessing CAS even if CAS is properly working.
Is there anything I can do for this particular situation?
I can see how it would seem like that. Yes, saved session/cookies were involved in the whole mess today, but they were browser cookies on the CAS site itself. So still nothing this code library could handle in any way.
For some reasons, I started to receive this error message about 20 or 30 minutes ago.
Right now, if I access BYU CAS on an incognito mode, I have no problem with CAS. But I can't access CAS without an incognito mode. I tried to clear browser cache, wait for a bit and try logging in again, and tried to log in on a sub url. However, nothing has been worked.
My guess is that I have to wait for an hour or so to resolve this issue. But after my web app launches, users shouldn't experience the same issue and wait for a long time to resolve it. How can I deal with the Internal Server Error in the future?