I added the security and OAuth2 resource-server starters and a security configuration so dictation endpoints require an authenticated caller. The module compiled with that setup. No token was issued and no request was authorized against a live identity provider.
- What worked
- The resource-server starter matched the existing API protection style, so the new service could declare the same authenticated-caller boundary in configuration.
- What got in the way
- Authorization behavior was not exercised, so filter order, audience checks, and failure responses remain unverified.