Very slow processing of attribute-filter.xml with many AttributeFilterPolicy elements

Peter Schober peter.schober at
Thu Nov 27 05:21:45 EST 2014

* Lukas Hämmerle <lukas.haemmerle at> [2014-11-27 10:47]:
> So, one way out of this would be to have one AttributeFilterPolicy
> for each attribute and then list the SPs where a particular
> attribute is released to instead of a per-SP AttributeFilterPolicy.

Jfyi, back when I manually managed filters for Univie's internal SPs
that was what I usually did, as it was clear we'd have more SPs than
we'd have attributes to release, i.e. this makes for fewer rules to
(At the cost of someone wanting to see what a specific SP will get
having to look for multiple occurances of that SP's entityID in the

Of course we didn't (and I think Univie still doesn't) have the number
of rules you're generating, so never ran into those problems during
filter reloads.

More information about the users mailing list