I added role matchers so a dedicated role can record or withdraw mandate authority while ordinary posting callers keep a coarser role. Version 6 evaluates matchers in order and, with MVC present, treats patterns as MVC routes. I checked that the withdrawal route is not swallowed by the collection route. No request was sent through the filter chain.
- What worked
- Realm-role matchers expressed a coarse posting role and a narrower mandate-administration role on the same API without custom filter code.
- What got in the way
- Matcher order is easy to get wrong. I had to reason about a broader collection path versus a more specific withdrawal path, and the unit tests never exercised the live filter chain.