Getting "No peer endpoint" on new installation

[George Boney]

Hello there,
      I have an issue I cannot seem to fix and I would appreciate any 
help you can provide.   I am using Shibboleth on a CentOS system (the 
SP) and testshib.org as the IDP.  Here is basically what happens
a)    Try to access 'secure' page
b)    Presented with login -- login as myself
c)    Get error "No Peer Endpoint"

I am at a loss at what more I can do to debug this.   It appears the IDP 
cannot find the system name in the metadata.  I have reloaded the 
metadata a couple of times, and recopied Shibboleth2.xml, restart shib 
and  http, etc.  (Though the last few times the Shibboleth2.xml has not 
had any changes in it.)

Any help or suggestions about how to troubleshoot that you can provide 
would be appreciated.

/Low Priority:  I also have a question about how to set this up so I can 
use different IDP's for different URL (/secure/dir1/* goes to IDP-A, 
/secure/dir2/* goes to IDP-B).   If you could recommend a good web 
source, white paper, book, etc.  that discusses this, I would appreciate 
it./
Thanks,
George Boney

*Detailed Flow and description.*
Try to access URL   "george.rmtcentral.net/secure/hello.cgi"
  (BTW, you can access "george.rmtcentral.net/unsecure/hello.cgi" just 
to see the expected result)
It asks for a login (myself/myself) and then presents a page that says:
-------------------------------------------------------------
Something horrible happened. ...
Error Message: No peer endpoint available to which to send SAML response
---------------------------------------------------------------
*The log file says*:
...
20:26:39.906 - DEBUG 
[edu.internet2.middleware.shibboleth.idp.profile.saml2.SSOProfileHandler:170] 
- Incoming request contains a login context and indicates principal was 
authenticated, processing second leg of request
20:26:39.907 - DEBUG 
[edu.internet2.middleware.shibboleth.common.relyingparty.provider.SAMLMDRelyingPartyConfigurationManager:128] 
- Looking up relying party configuration for 
https://george.rmtcentral.net/shibboleth
20:26:39.907 - DEBUG 
[edu.internet2.middleware.shibboleth.common.relyingparty.provider.SAMLMDRelyingPartyConfigurationManager:134] 
- No custom relying party configuration found for 
https://george.rmtcentral.net/shibboleth, looking up configuration based 
on metadata groups.
20:26:39.908 - DEBUG 
[edu.internet2.middleware.shibboleth.common.relyingparty.provider.SAMLMDRelyingPartyConfigurationManager:157] 
- No custom or group-based relying party configuration found for 
https://george.rmtcentral.net/shibboleth. Using default relying party 
configuration.
20:26:39.909 - WARN 
[org.opensaml.saml2.binding.AuthnResponseEndpointSelector:206] - Relying 
party 'https://george.rmtcentral.net/shibboleth' requested the response 
to be returned to endpoint with ACS URL 
'http://george.rmtcentral.net/Shibboleth.sso/SAML2/POST' 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
20:26:39.909 - ERROR 
[edu.internet2.middleware.shibboleth.idp.profile.AbstractSAMLProfileHandler:429] 
- No return endpoint available for relying party 
https://george.rmtcentral.net/shibboleth
*Metadata*
The metadata file ("Meda_George_Data."  Attached) shows
<!--This is example metadata only. Do *NOT* supply it as is without 
review, and do *NOT* provide it in real time to your partners.-->
<md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" 
xmlns:mdui="urn:oasis:names:tc:SAML:metadata:ui" 
ID="_19d9edf1851c00adc2a634793a1f9e536282b96c" 
entityID="https://george.rmtcentral.net/shibboleth">
   <md:Extensions xmlns:
  ....
         <md:SingleLogoutService 
Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" 
Location="https://george.rmtcentral.net/Shibboleth.sso/SLO/Redirect"/>
     <md:SingleLogoutService 
Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" 
Location="https://george.rmtcentral.net/Shibboleth.sso/SLO/POST"/>
     <md:SingleLogoutService 
Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact" 
Location="https://george.rmtcentral.net/Shibboleth.sso/SLO/Artifact"/>
     <md:AssertionConsumerService 
Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" 
Location="https://george.rmtcentral.net/Shibboleth.sso/SAML2/POST" 
index="1"/>
     <md:AssertionConsumerService 
Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST-SimpleSign" 
Location="https://george.rmtcentral.net/Shibboleth.sso/SAML2/POST-SimpleSign" 
index="2"/>
...
     <md:AssertionConsumerService 
Binding="urn:oasis:names:tc:SAML:1.0:profiles:artifact-01" 
Location="https://george.rmtcentral.net/Shibboleth.sso/SAML/Artifact" 
index="6"/>
   </md:SPSSODescriptor>
</md:EntityDescriptor>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130517/a1331c3f/attachment-0002.html 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130517/a1331c3f/attachment-0003.html