Skip to content

[Backend] Define bearerAuth/adminAuth security schemes referenced by route docs #541

Description

@ogazboiz

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

  • Either standardise all route docs on BearerAuth, or add bearerAuth and adminAuth definitions to components.securitySchemes
  • Every protected route shows a security requirement in /api-docs

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programbackendBackend related tasksdocsDocumentation

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions