Request missing SAMLResponse or TARGET form parameters.

[Florin Stingaciu]

Cantor,

You were correct. I adjusted the ACS URL on my IDP to
http://100.73.170.190/Shibboleth.sso/SAML2/POST, however now I'm receving
the following error:

POST targeted at (http://100.73.170.190/Shibboleth.sso/SAML2/POST), but
delivered to (http://server.com/Shibboleth.sso/SAML2/POST)

So server.com not available in the DNS. I make the initial request my
navigating to http://100.73.170.190/myapp.

I"m assuming this has to do with the ServerName directive in Apache. Is
there any way to ignore name mismatches? Or is there a more formal solution?

Thanks,

-F

On Wed, May 4, 2016 at 6:00 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> >However, when looking through the shibd logs, I find the following in the
> transaction logs:
>
> That log is basically meaningless. I took a quick look and it's just an
> artifact of it trying to log an error in the transaction log when it's
> forced to use the old transaction log format, which doesn't accomodate
> logging the right details. It makes every log entry look like a "new
> session" but it isn't really doing that, it's just sending a bunch of empty
> fields into the old log layout.
>
> I'm sure the trace logs include the relevant error(s) it's seeing, not to
> mention that it would be dumping the browser at an error page anyway.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160504/52ae17b8/attachment.html>