Auth

Description

When a server responds by 401/Unauthorized and challenge Alkaline for BASIC authentication with a WWW-Authenticate: BASIC realm=... header, Alkaline will attempt to use the credentials defined by this option. The domain value is ignored by this protocol.

In Alkaline for Windows NT, when a server responds by 401/Unauthorized and challenge Alkaline for Windows NT Challenge/Response NTLM authentication with a WWW-Authenitcation: NTLM header, Alkaline will attempt to negotiate a security context using credentials defined by this option. If the server rejects all credentials, negotiating with the current user context will also be attempted. Hence, if you are indexing an intranet as an authorized user, you do not need to specify any Auth options.

It is possible to specify as many Auth directives as required.

To set up such a protected zone Apache uses for example .htaccess and .htpasswd files. On Windows and IIS, the virtual directory security settings can be BASIC or Windows Authentication. Your browser usually pops a login window when you navigate to such a site.

Support for NTLM authentication was added in version 1.5.

Example

Auth Foo=foopassword
Auth Bar=barpassword
# Windows NT authentication
Auth ntdom\asearch=password