I am using Shibboleth Native SP for Apache 2.6.0 on CentOS 6.8.
The SP is configured with an <SSO> element that uses the
discoveryProtocol attribute with value "SAMLDS":
<SSO discoveryProtocol="SAMLDS" discoveryURL="https://myserver.com/discovery" EC
When I initiate session creation (a SAML2 SSO flow) like this
I receive a 302 Found with Location
That is, the discovery service is being told to send the
browser to a Shibboleth handler location at the target, which
in my use case does not exist.
I note that if I change the SP session creation parameter from
'target' to 'return' the Location has what I expect for the
value of 'return' that is passed to the discovery service.
Was the SP creation parameter name 'target' inadvertantly changed
Note that the attribute 'redirectLimit' on the <Sessions>
element is not set and so should have the default behavior of