Dothttp supports basic, digest and certificate auth inherently
For certificate auth docs visit this
Redefining authentication for each request is burden, with dothttp one can extend auth information from base request. check out more information on this here
Basic authentication is nothing but setting header
Authorization: <username:password with base64 encoded>
dothttp provides simple way to set basic authentication
Digest authentication is one of most used authentication mechanisms.
#AWS Signature v4 Authentication
Aws signature v4 authentication is used for interacting with amazonaws apis
awsauth(<accessId>, <secretKey>, <service>, <region>)
Windows NT LAN Manager (NTLM) is a challenge-response authentication protocol used to authenticate a client to a resource on an Active Directory domain.
It is an authentication scheme for HTTP, built around HMAC digests of requests and responses.
Every authenticated client request has an Authorization header containing a MAC (Message Authentication Code) and some additional metadata, then each server response to authenticated requests contains a Server-Authorization header thatauthenticates the response, so the client is sure it comes from the right server.
hawkauth(<id>, <key>, <algorithm like sha256...>)