Meteor.js and Shibboleth IP

[Peter Schober]

* Truby Voglund <tvoglund at mocodevco.com> [2015-07-01 16:23]:
> Thank you so much for the help.  I have now got the ACS Url to not
> be dynamic.

Good!

> But I monitor all calls to my SP and do not see any coming from the
> Shibboleth IdP (testShib).

I don't know what that means but the error message you (and me, and
everyone else) can get from the public testshib log files is pretty clear:

10:49:19.005 - WARN
[org.opensaml.saml2.binding.AuthnResponseEndpointSelector:206] -
Relying party 'http://tuadevshibbolet.cloudapp.net/shibboleth-sp'
requested the response to be returned to endpoint with ACS URL
'http://tuadevshibbolet.cloudapp.net/_saml/validate/shibboleth-idp/1ed79ec15dfd'
and binding 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST' however
no endpoint, with that URL and using a supported binding,  can be
found in the relying party's metadata

10:49:19.005 - ERROR
[edu.internet2.middleware.shibboleth.idp.profile.AbstractSAMLProfileHandler:447]
- No return endpoint available for relying party http://tuadevshibbolet.cloudapp.net/shibboleth-sp

Since the IDP says it doesn't have the quested ACS URL on record (for
that entityID) I guess this can only mean that testshib has
differing/stale metadata for your SP. I /think/ uploading with the same
file name will replace the existing metadata on testsib.

But you really need to start using the tools available to you.
I have no specical access or insight neither into your SP nor
testshib. Even the link to find the error log was provided in the
testhib error message.
-peter