I'm walking through the testshib instructions to setup a new SP, but
when I go to test it, i get a shibsp::ListenerException with the
message:
No destination registered for incoming message addressed to
(default/Login::run::SAML2SI).
I'm using the xml config file generated by testshib-two. The
shibboleth 2.1 rpms were installed when I was handed the server, but I
could wipe them and start fresh with the new 2.2 packages if I have
to. SELinux is disabled.
Any ideas on how to approach this?
Thanks
-jim
Start over. That error is impossible short of a totally corrupt codebase,
and I'm not even sure how you'd get it then.
-- Scott
That's what I needed to know. I'll update everything and start fresh.
Thanks!
-jim
If possible, try to do whatever you did involving testshib to replace the
configuration and see if it gives you a similar error. I can only think
there's a bug in there that hasn't come up before involving the
configuration changing underneath the code.
If not, no big deal.
-- Scott
>> That's what I needed to know. I'll update everything and start fresh.
>
> If possible, try to do whatever you did involving testshib to replace the
> configuration and see if it gives you a similar error. I can only think
> there's a bug in there that hasn't come up before involving the
> configuration changing underneath the code.
>
Couldn't replicate the error after I updated.
Just a heads up though, the testshib metatdata is still broken:
ERROR OpenSAML.MetadataProvider.XML : metadata intance failed manual
schema validation checking: AttributeAuthorityDescriptor must have at
least one AttributeService.
CRIT Shibboleth.Application : error building/initializing
MetadataProvider: Metadata instance failed manual schema validation
checking.
Thanks
-jim
> Just a heads up though, the testshib metatdata is still broken:
>
> ERROR OpenSAML.MetadataProvider.XML : metadata intance failed manual
> schema validation checking: AttributeAuthorityDescriptor must have at
> least one AttributeService.
> CRIT Shibboleth.Application : error building/initializing
> MetadataProvider: Metadata instance failed manual schema validation
> checking.
To finally squash this, I turned on validation checking, and found a
significant number of creative user-submitted metadata elements in
testshib-two-metadata.xml. They've been repaired and you should have
no problems now.
testshib-metadata.xml, associated with TestShib Classic, is deprecated
in a couple days, and will not be repaired.
Thanks again,
Nate.
Again, not your fault: this time some invalid metadata was submitted
by an OIOSAML user which had null valued for the xml:lang="" attribute
on several elements.
This has been fixed again, and I'm very sorry for the service
interruptions. I'll reiterate that we should look into adding better
validation of user-submitted XML or disable it entirely, but I'm
swamped for the next few months and will have no chance to do so.
Please download a fresh copy and try again.
Thanks,
Nate.
Fixed another one in another spot(an uncommon element which I didn't
realize needed xml:lang). It should be clean now.
Try, try again,
Nate.