Configured request matchers and JWT subject handling so only an identity-service role can attach a completed mandate and so postings require the caller subject to be on the named-poster list. No HTTP-layer security tests were run, so enforcement in a live request path was not observed.
- What worked
- Resource-server JWT authentication already in the app was enough to take the caller subject and map a service role onto the new attach route.
- What got in the way
- Path-matcher style (path patterns versus ant) needed a careful choice so the mandate route would actually match. That was reasoned from docs and existing config, not proven with a request test.