That's true, but it's not any different from the current behavior and/or code structure. Before this pull, the filtering process existed in CASImpl. This pull simply takes that bit of code and places it elsewhere such that it can be more easily augmented. The filtering process and the execution of the chain still exists in CASImpl. Much like now where the services management tool does not have the responsibility of filtering attributes.

If I understand correctly, if you're proposing that the filtering process should also be moved into the services management tool, it might be better captured in a separate JIRA. That request appears to be more complicated than simply providing abstractions around the attribute filtering process.