By: John Feulner user 28 Dec 2015 at 2:54 p.m. CST

6 Responses
John Feulner gravatar
Hey all, Another challenge. After getting authentication setup and logins working I am now attempting to test SAML with TestShib. According to the documentation, I went to https://[URLOFSSO]/idp/shibboleth - But all I get is a white page. However the developer tab in chrome states is a 404. Shibboleth iDP is installed. Thoughts?

By Michael Schwartz Account Admin 28 Dec 2015 at 3:05 p.m. CST

Michael Schwartz gravatar
Not getting the Shibboleth IDP metadata is a really bad sign. Are you sure you selected the shibboleth IDP component when you ran setup.py? Do you see anything in the Apache httpd logs or /opt/idp/logs files that might indicate a problem with the hostname perhaps?

By John Feulner user 28 Dec 2015 at 3:13 p.m. CST

John Feulner gravatar
Let me give this a good ol'reinstall **JUST** to be sure.

By John Feulner user 28 Dec 2015 at 4:07 p.m. CST

John Feulner gravatar
That was it. A Reinstall fixed it. ![Facepalm](http://i.imgur.com/6mBNcE5.gif "Picard Facepalm")

By Michael Schwartz Account Admin 28 Dec 2015 at 4:16 p.m. CST

Michael Schwartz gravatar
BTW, I just added a fix to community-edition-setup so you can see if the Shib IDP was installed... in the future you can grep setup.properties.last for installSaml but this will probably not make it until version 2.4.2.

By John Feulner user 29 Dec 2015 at 11:36 a.m. CST

John Feulner gravatar
So I was able to recreate the issue by restarting the services. Once I restarted them, the Shibboleth iDP no longer responded. Version 2.4.0 from CentOS 6 repository. Installed on CentOS 6.5 Ok, so it's fixed now by stopping Tomcat. Waiting for that, starting it, and then starting HTTPD. After that, all was right with the world again. Very odd. Going to dig around in logs and see what I can find and see if I can break it again. FOR SCIENCE

By William Lowe user 07 Jan 2016 at 2:18 p.m. CST

William Lowe gravatar
Sounds good, John. Let us know your findings. Thanks!