Shibboleth SP Leading to 404

[Jeff Gehly]

Sorry about the confusion (it's been a long day of running into a mental
brick wall with this problem).  I had setup the WebLogic IdP to log SAML2
events and that's what I meant in my statement about the IdP redirect.  The
IdP log shows an HTTP GET with a redirect call in it that specifies a hashed
SAMLRequest string ("GET /saml2/idp/sso/redirect?SAMLRequest=<hashed
string>").  This GET call is where the 404 is happening.  

Part of what this particular IdP does is issue a redirect back to the
originally requested resource after authenticating the user.  I wasn't sure
if somehow Shibboleth was misconfigured and responsible for the 404 returned
by that redirect or not.


I didn't really know for sure if the problem resides with Shibboleth's SP
but by this point I've gotten sort of desperate.  I reached out here in
hopes that either someone could spot what I had done wrong in setting up
Shibboleth, or help me eliminate Shibboleth as the problem.  Your response
was actually quite helpful, because you've just given me some solid proof
that my problem is something on the IdP.  


Just out of curiosity, would a lack of log activity on the Shibboleth SP
indicate that the IdP is not returning a SAML2 message?  When I get the 404,
there is absolutely no activity from the SP.  





--
View this message in context: http://shibboleth.1660669.n2.nabble.com/Shibboleth-SP-Leading-to-404-tp7585393p7585396.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.