moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-11-16 06:25:03 -05:00
Code Issues Releases Wiki Activity

docs: Added Kerberos V5 and NTLM domain information to --user

Browse Source
This commit is contained in:
Steve Holme 2014-08-15 21:36:35 +01:00
parent 0574196acb
commit 7679cb3fa8
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/curl.1
View File

@ -1627,6 +1627,19 @@ The user name and passwords are split up on the first colon, which makes it
impossible to use a colon in the user name with this option. The password can, impossible to use a colon in the user name with this option. The password can,
still. still.
When using Kerberos V5 with a Windows based server you should include the
Windows domain name in the user name, in order for the server to succesfully
obtain a Kerberos Ticket. If you don't then the initial authentication
handshake may fail.
When using NTLM, the user name can be specified simply as the user name,
without the domain, if there is a single domain and forest in your setup
for example.
To specify the domain name use either Down-Level Logon Name or UPN (User
Principal Name) formats. For example, EXAMPLE\user and user@example.com
respectively.
If you use a Windows SSPI-enabled curl binary and perform Kerberos V5, If you use a Windows SSPI-enabled curl binary and perform Kerberos V5,
Negotiate or NTLM authentication then you can tell curl to select the user Negotiate or NTLM authentication then you can tell curl to select the user
name and password from your environment by specifying a single colon with this name and password from your environment by specifying a single colon with this