Shibboleth2.xml One host element containing two path elements, second path is not routing
Cantor, Scott
cantor.2 at osu.edu
Fri Feb 27 18:41:46 EST 2015
On 2/27/15, 6:31 PM, "Michael A Grady" <mgrady at unicon.net> wrote:
>
>The entityID attribute in the ApplicationOverride element needs to be the
>entityID of this "path-based SP", NOT the entityID of the IdP. And that
>IdP will need to have metadata for each of these path-based SPs, with
>distinct ACS endpoints. You are defining distinct Sps, one per company
>IdP, and you need to carry this distinction thru to everything.
Didn't notice that. That wouldn't be an advisable thing to do, but there's
just so much messy stuff here.
>> <Sessions lifetime="28800" timeout="3600" relayState="ss:mem"
>>checkAddress="true" handlerSSL="true" cookieProps="https">
>> <SSO entityID="http://saml.company1.com"
>> discoveryProtocol="SAMLDS"
>> discoveryURL="https://www2.accp.company1.com/saml?target=sp_name"
>> target="https://test.sp_company.com/SignIn/path1">
This is all wrong also. You don't set an entityID *and* set discovery
settings, and you sure don't want to set target there, that's a very
obscure thing to do.
-- Scott
More information about the users
mailing list