include statements in xml configuration files?

[Cantor, Scott]

On 2/19/21, 2:39 PM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:

>    I think I follow you here. You're saying externally generate a file that contains a metadata entity attribute filter with the
> right XML bits in it to add the entity attributes to the specified entity IDs then include it by reference in the metadata
> provider block.

It's outside-in, there is nothing in the metadata provider, that's the point of it.

> What would the XML look like in the metadata provider block to attach a metadata filter by reference?

Nothing there, the separate file is all there is.

<MetadataFilter xsi:type="ByReference">
	 <MetadataFilters providerRef="InCommonMD">
		<MetadataFIlter ... />
		<MetadataFIlter ... />
	</MetadataFilters>
</MetadataFilter>

https://wiki.shibboleth.net/confluence/display/IDP4/ByReferenceFilter

> Of course, the beauty of the regex solution is, as long as you have a reliable regex pattern, it's a once and done.

I would do it that way, but that's just a special case.

> Like you said, the regex adds a little computing power as it has to be built each time. There's not a way to avoid that while
> still using the regex, is there? I'm not thinking of one.

A Pattern can be built and compiled in a bean definition and injected into a script as a custom object, avoiding compiling it every time.

-- Scott