We have a Shibboleth-protected Moodle installation at the college I work for. I'm getting an error "Request missing SAMLRequest or SAMLResponse form parameter," when I try to log in from home.
This happens with any username/password combination, on any browser and I've tested on different hardware all with the same result. The odd thing is that I don't get this error even using the same browsers, same hardware and same logins from other connections (both inside college and outside).
It's also only happening on that particular SP. The login against the IDP works and will log me into other Shibboleth protected sites at the college.
Is there any reason why I could see different behaviour like this for different ISPs? I'm completely out of ideas and can't find any reference to anyone having a similar issue.
I should probably mention that we've been running Shibboleth in front of most of our webapps for over a year with thousands of users and have encountered this problem only once or twice before and it has spontaneously resolved itself after a few days. This one seems a little more stubborn, however.
Thanks for any help anyone can offer :)
Kevin Hughes
Lead Web Developer
South Devon College
This email and any attachments may contain information which is confidential to South Devon College. If you are not the intended recipient, please notify the sender immediately by replying to this email and then delete the email without making any copies or using it in any way.
South Devon College accepts no legal responsibility for the contents of the message. Any views expressed in the message are those of the sender and may not reflect the views of the College.
Although any attachments to the message will have been checked for viruses before transmission, you are urged to carry out your own virus check before opening attachments, because South Devon College accepts no responsibility for loss or damage caused by software viruses.
--
To unsubscribe from this list send an email to users-un...@shibboleth.net
A timeout in Apache would be something I've seen resembling this, but not
that particular error. Somebody would probably need to get a packet trace
of the submission.
To rule it out, I'd make sure Live Headers doesn't show anything unusual
on the client end.
-- Scott