Telegram: https://t.me/+DOylgFv1jyJlNzM0
Why this matters
backend/src/config/swagger.ts defines only one security scheme, BearerAuth (capitalised). But several route @openapi blocks reference undefined schemes:
bearerAuth (lowercase) in routes/v1/stream.routes.ts, routes/v1/admin.routes.ts, controllers/stream/cancel.ts, routes/v1/streams/withdraw.ts
adminAuth in routes/adminRoutes.ts
Because these scheme names don't exist in components.securitySchemes, Swagger UI renders those endpoints as unauthenticated (no lock icon, no auth hint).
Acceptance criteria
Files to touch
backend/src/config/swagger.ts
- route files referencing
bearerAuth/adminAuth (if standardising names)
Out of scope
- Changing the actual auth middleware behaviour.
Telegram: https://t.me/+DOylgFv1jyJlNzM0
Why this matters
backend/src/config/swagger.tsdefines only one security scheme,BearerAuth(capitalised). But several route@openapiblocks reference undefined schemes:bearerAuth(lowercase) inroutes/v1/stream.routes.ts,routes/v1/admin.routes.ts,controllers/stream/cancel.ts,routes/v1/streams/withdraw.tsadminAuthinroutes/adminRoutes.tsBecause these scheme names don't exist in
components.securitySchemes, Swagger UI renders those endpoints as unauthenticated (no lock icon, no auth hint).Acceptance criteria
BearerAuth, or addbearerAuthandadminAuthdefinitions tocomponents.securitySchemes/api-docsFiles to touch
backend/src/config/swagger.tsbearerAuth/adminAuth(if standardising names)Out of scope