Looping requests when ApplicationOverride used

[Cantor, Scott]

On 3/29/17, 11:22 AM, "users on behalf of tullrich72" <users-bounces at shibboleth.net on behalf of timo.ullrich at bluewin.ch> wrote:

> the basic idea was to use different MetaData based on incoming query
> parameters.

Don't do that. Metadata should be loaded once, globally, and everything else should be based on attributes and evaluating other policy.

> While all works fine for the ApplicationDefaults configuration,
> I end up in a loop when the ApplicationOverride configuration is used. 

Then you did not map all the relevant URLs to the right override, including the handler for the override.

> For simplification the override configuration is currently fully inheriting from
> defaults config (Sessions element has been redefined).

And you cannot do that, not for path-based overrides. This is all discussed in the wiki. Path overrides require a modified handlerURL.

-- Scott