Skip to content

Commit

Permalink
CURLOPT_USERNAME.3: Added Kerberos V5 and NTLM domain information
Browse files Browse the repository at this point in the history
This repeats what has already been documented in both the curl manpage
and CURLOPT_USERPWD documentation but is provided here for completeness
as someone may not especially read the latter when using libcurl.
  • Loading branch information
captain-caveman2k committed Aug 16, 2014
1 parent 29240cb commit 97f6049
Showing 1 changed file with 16 additions and 0 deletions.
16 changes: 16 additions & 0 deletions docs/libcurl/opts/CURLOPT_USERNAME.3
Expand Up @@ -37,6 +37,22 @@ user name to use for the transfer.
authentication. You should not use this option together with the (older)
\fICURLOPT_USERPWD(3)\fP option.

When using Kerberos V5 authentication with a Windows based server, you should
include the domain name in order for the server to successfully obtain a
Kerberos Ticket. If you don't then the initial part of the authentication
handshake may fail.

When using NTLM, the user name can be specified simply as the user name
without the domain name should the server be part of a single domain and
forest.

To include the domain name use either Down-Level Logon Name or UPN (User
Principal Name) formats. For example, EXAMPLE\user and user@example.com
respectively.

Some HTTP servers (on Windows) support inclusion of the domain for Basic
authentication as well.

To specify the password and login options, along with the user name, use the
\fICURLOPT_PASSWORD(3)\fP and \fICURLOPT_LOGIN_OPTIONS(3)\fP options.
.SH DEFAULT
Expand Down

0 comments on commit 97f6049

Please sign in to comment.