guides/user/Command-line-user-interface.md

@@ -126,6 +126,7 @@ in the [knowledge base](http://support.arachni-scanner.com/kb/).
     * [Authentication](#http-authentication)
         * [Username (--http-authentication-username)](#http-authentication-username)
         * [Password (--http-authentication-password)](#http-authentication-password)
+        * [Type (--http-authentication-type)](#http-authentication-type)
     * [Proxy (--http-proxy)](#http-proxy)
     * [Proxy authentication (--http-proxy-authentication)](#http-proxy-authentication)
     * [Proxy type (--http-proxy-type)](#http-proxy-type)
@@ -921,7 +922,7 @@ Cookies, in the format of a `Set-Cookie` response header, to be sent to the web
 
 <h3 name='http-authentication'><a href='#http-authentication'>Authentication</a></h3>
 
-The HTTP authentication type is detected automatically, all that is necessary is specifying
+By default, the HTTP authentication type is detected automatically, all that is necessary is specifying
 the <a href='#http-authentication-username'>username</a> and <a href='#http-authentication-password'>password</a>.
 
 The only situation where that's not the case is when using Kerberos. In that case a ticket needs
@@ -955,6 +956,24 @@ Username to use for HTTP authentication.
 
 Password to use for HTTP authentication.
 
+<h4 name='http-authentication-type'><a href='#http-authentication-type'>Type (--http-authentication-type)</a></h4>
+
+**Expects**: `string`
+
+**Default**: `auto`
+
+**Multiple invocations?**: `no`
+
+
+HTTP authentication type to use, available types are:
+
+- `auto` -- Default
+- `basic`
+- `digest`
+- `digest_ie`
+- `negotiate`
+- `ntlm`
+
 <h3 name='http-proxy'><a href='#http-proxy'>Proxy (--http-proxy)</a></h3>
 
 **Expects**: `server:port`