Can Swagger describe an API that uses Digest Authentication?

[Rob C.]

Can swagger be used to accurately describe a resource that is protected by digest authentication (RFC 2617)? From the spec it looks like it only supports basic auth, api key or oath.  We have several services that use digest and were looking to standardize on swagger as our API Description Language. 

[Ron Ratovsky]

https://groups.google.com/d/topic/swagger-swaggersocket/r1UaZ4i8guU/discussion may help, at least for now.

There's also https://github.com/swagger-api/swagger-spec/issues/344.

On Tue, Aug 11, 2015 at 1:35 PM, Rob C. <rob...@gmail.com> wrote:

Can swagger be used to accurately describe a resource that is protected by digest authentication (RFC 2617)? From the spec it looks like it only supports basic auth, api key or oath.  We have several services that use digest and were looking to standardize on swagger as our API Description Language. 

--
You received this message because you are subscribed to the Google Groups "Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggers...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

-----------------------------------------

http://swagger.io
https://twitter.com/SwaggerApi
-----------------------------------------