[MGNLRESTCL-218] Open API securityScheme is null Created: 05/Sep/23  Updated: 28/Nov/23

Status: Accepted
Project: REST Client
Component/s: None
Affects Version/s: 2.0.4
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File secuirtyScheme.png    
Issue Links:
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: RESTClient 2024
Team: DeveloperX

 Description   

The Open API security scheme is defined at a global level.

{
  "openapi": "3.0.2",
  "info": {
    "title": "Search API",
    "version": "1.0.0",
    "description": "API to add to and delete from index"
  },
  ...
  ...
  "components": {
    ...
    ...
    "securitySchemes": {
      "adb2cBearerToken": {
        "type": "http",
        "scheme": "bearer",
        "bearerFormat": "JWT"
      }
    },
    "headers": {},
    "responses": {},
    "parameters": {}
  },
  "tags": [],
  "security": [
    {
      "adb2cBearerToken": []
    }
  ]
}

The OpenApiDefinitionMapper doesn't seem to consider this as a possibility and there is no way to explicitly define a security scheme in the definition file. Ultimately that leaves the security scheme set as null.


Generated at Mon Feb 12 10:44:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.