multiplexing IdP configurations

[Walter Forbes Hoehn (wassa)]

If I understand your question correctly, this is already doable… even easy.  One of my prod IdP nodes, for instance, services all of the following endpoints:

https://sso.memphis.edu/idp/SAML2/Redirect/SSO
https://sso.memphis.edu/idp/Shibboleth/Redirect/SSO
https://sso1.memphis.edu/idp/SAML2/Redirect/SSO
https://sso1.memphis.edu/idp/Shibboleth/Redirect/SSO

Depending on how the endpoints vary, this may require changes to the host or container configuration. In the case where you just want to effect the RHS, you can do something like the following in webflow-config.xml:

        <webflow:flow-location id="SAML2/Redirect/SSO" path="../system/flows/saml/saml2/sso-redirect-flow.xml" />
        <webflow:flow-location id=“Shibboleth/Redirect/SSO" path="../system/flows/saml/saml2/sso-redirect-flow.xml" /> <!-- WFH: supports legacy config -->

Does this help?

-WFH


> On Mar 27, 2015, at 2:59 PM, Tom Scavo <trscavo at gmail.com> wrote:
> 
> On Fri, Mar 27, 2015 at 1:36 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
>> 
>> If you're trying to add endpoints, that's not new, even V2 could do that
> 
> If it can do that, I'll be pleasantly surprised (and embarrassed about
> all the people who have sweat brass tacks because of my bad advice :)
> 
>> but I don't think that's what you're after...
> 
> You can only have one inbound HTTP-Redirect endpoint (e.g.) at the
> IdP. If you want to change the location of that endpoint, you
> necessarily break interoperability until your SP partners have updated
> their metadata.