Swagger UI is not challenging with Basic Auth to the openAPI endpoint

I have a JAX-RS application, and we are using OpenAPI/Swagger to view all the APIs. I want to protect the OpenAPI Endpoint with Basic Auth (URL: http://localhost:8090/openapi). On the first request to the endpoint, I am setting the response header with 'WWW-Authenticate' and the value 'Basic realm="XXXX"'. This is working fine if I open the URL in the chrome browser PFA chrome.jpg. However, if I open the same URL in Swagger UI, it is not challenging with a username and password and showing 401 page PFA swagger.jpg.

Response Header from Swagger
Content-Security-Policy:default-src 'none'; frame-ancestors 'none'
Content-Type:application/json
Referrer-Policy:strict-origin-when-cross-origin
Strict-Transport-Security:max-age=31536000
WWW-Authenticate: Basic realm="XXXX"
X-Content-Type-Options:nosniff
X-Frame-Options:SAMEORIGIN
X-Xss-Protection:1
Accept:application/json,/

Q&A (please complete the following information)

• OS: Windows
• Browser: Chrome
• Version: 120.0.6099.217 (Official Build) (64-bit)
• Method of installation: NA
• Swagger-UI version: 5.11.0
• Swagger/OpenAPI version: OpenAPI 3.0
  
  

Reproduce the request to http://localhost:8090/openapi through Swagger UI 5.11.0 and compare it with the same URL in Chrome. Start from the OpenAPI endpoint request and its WWW-Authenticate: Basic realm="XXXX" response; done means Swagger UI handles the protected endpoint as expected instead of displaying a 401 page.