Multiple IDP Entity IDs with 1 IDP

[Brian Reindel]

What Scott is saying is that if you're using Apache then you don't
need the request mapper at all. The applicationId you provide in a
location (content) block in Apache will map to the override with the
same application ID in shibboleth2.xml. So for example, in your vhost
configuration:

    <Location />
        AuthType shibboleth
        ShibUseHeaders On
        ShibRequestSetting applicationId yourIdGoesHere
        ShibRequestSetting requireSession 1
        Require valid-user
    </Location>

Then your override:

        <ApplicationOverride id="yourIdGoesHere"
entityID="https://www.example.org">
            ...
        </ApplicationOverride>

If you don't provide an application ID in one of your vhosts then it
will get mapped to the ApplicationDefaults settings. So you now have a
default vhost and an override vhost with a different applicationId.

On Thu, Jul 25, 2013 at 4:32 PM, bs_sunil <bssunil74 at yahoo.com> wrote:
> I was referring to your earlier point that is "two vhosts to act as separate
> SP entityID" is a case for request mapper and application override.
>
> So, I put up the request mapper for the 2 vhosts and the application
> override. Appreciate if you could let me know how do I implement it further.
>
> Thanks
> Sunil
>
>
>
> --
> View this message in context: http://shibboleth.1660669.n2.nabble.com/Multiple-IDP-Entity-IDs-with-1-IDP-tp7588769p7588809.html
> Sent from the Shibboleth - Users mailing list archive at Nabble.com.
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net