404 Not Found on /profiles/SAML2/Redirect/SSO

By: Karl Jaro user 11 May 2016 at 4:07 a.m. CDT

11 Responses
Karl Jaro gravatar
Hello Gluu, I've turned on my working server (was working smoothly for 2 weeks before I turned it off - we are done testing) and I encountered this problem (Gluu 2.4.2), I also tried clean installing 2.4.3 and still encounter the same problem. ![enter image description here](http://s32.postimg.org/h0x3yht7p/Capture.png "enter image title here")
closed

Answers

By Mohib Zico Account Admin 11 May 2016 at 4:12 a.m. CDT

Copy
Mohib Zico gravatar
Couple of points to check: - Check if 443 is still open and working or not. - Stop tomcat, clean idp logs and restart tomcat. See if there is any error in idp-process.log and wrapper.log or not. - If you get any error. Please share the stack trace.

By Karl Jaro user 11 May 2016 at 4:36 a.m. CDT

Copy
Karl Jaro gravatar
Hello Mohib, 443 is open as I could access the GUI itself, just that I can't use the SSO because I can't access the SAML2/Redirect/SSO. idp logs are clean as I've done a fresh install. I'll be checking idp-process.log and wrapper.log

By Michael Schwartz Account Admin 11 May 2016 at 4:52 a.m. CDT

Copy
Michael Schwartz gravatar
Its a very strange issue. 443 is definitely open, because this error is coming from the apache web server (which is saying it can't find the site). I would look into the binding of the hostname to the ethernet interface in the apache htttp config. Is it possible that the apache web server virutalhost is not mapped properly to the hostname?

By Karl Jaro user 11 May 2016 at 4:57 a.m. CDT

Copy
Karl Jaro gravatar
Hello Michael, I've been using AWS ever since. I've been working with Mohib for my SSO errors back then (I hope he remembers me), I've made it work and I've been testing it out for a week back then. I stopped development and have stopped configuring it as it has been stable. I've came back to the server, because our IT Manager wants to see the results that I've made and I've been greeted with this error.

By Karl Jaro user 11 May 2016 at 4:58 a.m. CDT

Copy
Karl Jaro gravatar
I left the server at version 2.4.2, and have since not encountered an error, came back and I encountered it - figured out to clean install a new 2.4.3 version and I'm still encountering the problem. btw I already tried /profiles/ and /profile/ with no success

By Michael Schwartz Account Admin 11 May 2016 at 5:05 a.m. CDT

Copy
Michael Schwartz gravatar
I read that... I don't know what changed, but I think you need to start troubleshooting the basics. The web server can't find the juntion. Why not? Check all the logs to find out why either the respective web application file didn't start in tomcat, or the webserver is not mapping to the correct backend.

By Karl Jaro user 11 May 2016 at 5:21 a.m. CDT

Copy
Karl Jaro gravatar
How will I be able to check if it's mapping correctly to the backend, I haven't changed any since coming back.

By Michael Schwartz Account Admin 11 May 2016 at 5:31 a.m. CDT

Copy
Michael Schwartz gravatar
Saying "I didn't change anything" is not going to get your problem solved! Gluu Server uses Apache httpd. Check the config in `/etc/apache2` Also, you did not provide any details from the logs. There is no way we can help you if you don't provide the configuration and logs.

By Karl Jaro user 11 May 2016 at 11:13 p.m. CDT

Copy
Karl Jaro gravatar
I fixed it by replacing "profile/SAML2/Redirect/SSO" to "/idp/profile/SAML2/Redirect/SSO" please update your documentation regarding Google SSO. Thank you!

By Mohib Zico Account Admin 12 May 2016 at 3:59 a.m. CDT

Copy
Mohib Zico gravatar
Thanks for the note, Karl. Seems like screenshot is showing proper setup but description below that screenshot is lacking proper syntax. We are fixing the doc now.

By Karl Jaro user 12 May 2016 at 5:18 a.m. CDT

Copy
Karl Jaro gravatar
You're welcome! Appreciate the quick response as always.

Post an answer