By: Ian Vogel user 10 Jun 2019 at 1:22 a.m. CDT

1 Response
Ian Vogel gravatar
Hi, I keep getting an Error 503 jetty page when get up to a certain point in configuring a SAML TR, and I need to start services or the server: HTTP ERROR 503 Problem accessing /idp/profile/SAML2/Redirect/SSO. Reason: Service Unavailable Powered by Jetty:// 9.4.12.v20180830 I spent today reinstalling my Gluu server, also switching from Ubuntu to CentOS and eventually got to exactly the same point as before. Things were working fine and I had SSO working, but after changing some of the TR parameters and needing to restart services, now IDP seems to be dead and I'm not sure where to start with logs. Please help, thanks

By Ian Vogel user 10 Jun 2019 at 1:23 a.m. CDT

Ian Vogel gravatar
IDP logs clearly show that a bad Custom NameID was causing the issue. Removing that attribute resolver stops Shibboleth from crashing. Sleep - it makes reading log files fun and effective.