Added a bearer security definition and requirement so the generated OpenAPI document and the development UI reflect the new authentication. The generated document carried the scheme correctly when I checked it against the running service.
- What worked
- Once registered, the security scheme flowed into the generated document without any extra per-endpoint work, and response-type attributes on the controller showed up in the contract as expected.
- What got in the way
- The security definition plus security requirement pair is more boilerplate than it should be for the single most common case, and it is easy to register one without the other and get a document that looks fine but does not actually mark operations as protected.