SSO is a pain

[PaulHomes]

Not sure if the patch has been rolled out yet, but I just got the HTTP 500 error again (it's Monday morning in Australia).

[Reeza]

I've been getting 401 errors over the past few days. More than usual. 

[Reeza]

[ChrisHemedinger]

Still working on it @Reeza.  Our weekend attempt to patch this failed some tests, so it was rolled back.  I think attempt #2 is scheduled for late this week.

[Kurt_Bremser]

Just had the failure once again. Cleaned out all cookies from sas.com and communities.sas.com to get a clean login form.

[Reeza]

Same here. 

[Tom]

Much simpler to just open the http://support.sas.com page and sign-out.  Then you can goto to Community page and it will work again.

[Kurt_Bremser]

---

@Tom wrote:

Much simpler to just open the http://support.sas.com page and sign-out.  Then you can goto to Community page and it will work again.

---

Thanks for the tip. Will try that next time I'm stuck on the tablet.

[ChrisHemedinger]

There was a minor update to our single-signon software last night -- an update that did not require an outage, so no announcement was made.  However, this might have been a trigger for this particular occurence of the cookie-mismatch.

[Tom]

@ChrisHemedinger

Can you just get them to update the "HTTP Status 500" error page so that it includes a link to the http://support.sas.com page?

HTTP Status 500 - Unable to do Single Sign On or Federation.

type Status report

message Unable to do Single Sign On or Federation.

description The server encountered an internal error that prevented it from fulfilling this request.

---

Apache Tomcat/8.0.20