One idp application serving as two idps (with different entityIDs)

[Cantor, Scott]

On 8/20/15, 6:53 PM, "dev on behalf of Tom Zeller" <dev-bounces at shibboleth.net on behalf of tzeller at dragonacea.biz> wrote:

>
>> On Aug 20, 2015, at 11:43 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:
>> 
>> On 8/20/15, 4:27 AM, "dev on behalf of Andrea Biancini" <dev-bounces at shibboleth.net on behalf of andrea.biancini at garr.it> wrote:
>> 
>>> Hi all,
>>> I am trying to figure out if there is a configuration (or code 
>>> extension) that could permit one single IdP to operate with two 
>>> different entityIDs.
>> 
>> Yes, to a degree. The entityID used can be set on a per-RP, per-profile basis.
>
>With Scott’s caveats, and this is not exactly what was asked for, but here is some example relying-party.xml configuration which overrides the IdP (responder) entityID based on the RP entityID :
>
><bean
> id=“MyDefaultRelyingPartyByName"
> parent=“RelyingPartyByName"
> abstract="true”>
> <property name=“profileConfigurations"
>  value="#{@'shibboleth.DefaultRelyingParty'.profileConfigurations.values()}" />
></bean>

Now that's a trick I haven't seen.

We should put some examples like that into the wiki.

-- Scott