[JIRA] Created: (SSPCPP-445) RequestInitiator metadata generated in a case where it shouldn't be

[Ian Young (JIRA)]

RequestInitiator metadata generated in a case where it shouldn't be
-------------------------------------------------------------------

                 Key: SSPCPP-445
                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-445
             Project: Shibboleth SP - C++
          Issue Type: Bug
          Components: Other
    Affects Versions: 2.4.3
            Reporter: Ian Young
            Assignee: Scott Cantor


If you have a bare "WAYF" type SessionInitiator in shibboleth2.xml as follows:

   <SessionInitiator id="foo" Location="/foo" acsIndex="5"
      URL="...whatever..."/>

Then the automatically generated metadata will include something like this:

   <init:RequestInitiator xmlns:init="urn:oasis:names:tc:SAML:profiles:SSO:request-init"
      Binding="urn:oasis:names:tc:SAML:profiles:SSO:request-init"
      Location="https://sh2testsp1.iay.org.uk/Shibboleth.sso/foo"/>

However, actually sending a session initiation message to that location results in a configuration error:

shibsp::ConfigurationException at (https://sh2testsp1.iay.org.uk/Shibboleth.sso/foo)

Configured Shibboleth handler failed to process the request.

It would be better not to only endpoints with that binding if the configured session initiator supported it.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira