Skip to content

Fix for Swagger Authorization Issue.

Type of change

Bug Fix

Please provide link to gitlab issue or ADR(Architecture Decision Record)
#95 (closed)

Does this introduce a change in the core logic?

  • No change in core logic. It is a change in swagger.

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • The change is in search-core module, so it affects all CSPs.

Does this introduce a breaking change?

  • No

What is the current behavior?

Querying any API through Swagger results in 403 response. This is due to the Authorization header not being picked up.

What is the new/expected behavior?

Querying API through Swagger is returning expected response.

Have you added/updated Unit Tests and Integration Tests?


Any other useful information

In all other services, the authorizationScope selected for Swagger is "Authorization" (code link). However, in search it is "JWT" (code link)

Due to this, calling APIs through Swagger is resulting in 403 response. This MR aims at fixing this issue.

Merge request reports