Digest access authorization

[mattias-kindborg-at-work]

Content & configuration

Swagger/OpenAPI definition:

openapi: 3.0.3
info:
 title: Some API
 version: 1.0.0
paths:
 /foo:
   get:
     responses:
       '200':
         description: Some description
components:
 securitySchemes:
   digestAuth:
     type: http
     scheme: digest
security:
 - digestAuth: []

Is your feature request related to a problem?

When trying to authorize using Swagger UI I get digestAuth HTTP authentication: unsupported scheme 'digest' displayed in the UI. I'm guessing that digest auth isn't supported?

Describe the solution you'd like

I would like digest auth to work against devices that support the protocol.

Describe alternatives you've considered

I'm open to contribute this functionality if you deem that digest auth is applicable to this project.

[AV25242]

Any considerations to make digest authentication be available with OpenAPI spec ?

[sydpz]

I also need this feature

[heibaijian]

Is there any plan for this requirement?

[rozzilla]

+1

[bambamboole]

I am currently converting our legacy docs to OAS 3 and am stumbling over the same issue. No option to describe digest auth. So also a +1 form me :)

[mbivlsi]

We are also waiting for this feature.

[chris-sun-star]

I'm also looking forward to this feature, for now, I've implemented a digest-proxy to workaround, if you just want to try the api on swagger-ui webpage, you can setup the proxy server and modify the host in the api definition to point to the proxy server's address and then try the api without the need to pass the authorization information. here are the references: https://github.com/chris-sun-star/digest-proxy/ https://hub.docker.com/r/wizardonmoon/digest-proxy/tags