A gap in the dynamic configuration support in the relying-party layer is the ability to turn profiles on and off with a runtime predicate (e.g., a metadata tag to enable SAML 1.1 without a relying party override specific to that tag).
We can't add anything to ProfileConfiguration, but a new ConditionalProfileConfiguration can be injected into the hierarchy and trigger runtime eval.
This is a little "unusual" in the sense that it doesn't play quite as well with the new MDDriven support because it defaults to enabled. Since the common task here is to enable a profile conditionally, you really can't tag every SP as "off" as a way to override the default condition.
What works better is to either explicitly change the DefaultRelyingParty's SAML 1 bean with a condition based on a tag, or to override the activationCondition in user-space with an MDDriven Predicate but set the default on it to false, which is something that makes sense in user land.
A gap in the dynamic configuration support in the relying-party layer is the ability to turn profiles on and off with a runtime predicate (e.g., a metadata tag to enable SAML 1.1 without a relying party override specific to that tag).
We can't add anything to ProfileConfiguration, but a new ConditionalProfileConfiguration can be injected into the hierarchy and trigger runtime eval.