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

[Scott Cantor (JIRA)]

    [ https://issues.shibboleth.net/jira/browse/SSPCPP-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119#comment-14119 ] 

Scott Cantor commented on SSPCPP-445:
-------------------------------------

I was originally going to say that my impression was that the spec permits entityID to be omitted, which is true, but I think that it's outside of the spirit of the language to advertise an endpoint that actually breaks on a defined parameter. So I guess I agree, WAYF only shouldn't generate it.

I also can think of some specific cases that would be errors as stand alone handlers, so no reason not to block those, and that also prevents them from generating metadata.

The WAYF case is the outlier because it could stand alone without breaking.

> 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 only to generate 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