| lh | 9ed821d | 2023-04-07 01:36:19 -0700 | [diff] [blame] | 1 | Long: user |
| 2 | Short: u |
| 3 | Arg: <user:password> |
| 4 | Help: Server user and password |
| 5 | --- |
| 6 | Specify the user name and password to use for server authentication. Overrides |
| 7 | --netrc and --netrc-optional. |
| 8 | |
| 9 | If you simply specify the user name, curl will prompt for a password. |
| 10 | |
| 11 | The user name and passwords are split up on the first colon, which makes it |
| 12 | impossible to use a colon in the user name with this option. The password can, |
| 13 | still. |
| 14 | |
| 15 | When using Kerberos V5 with a Windows based server you should include the |
| 16 | Windows domain name in the user name, in order for the server to successfully |
| 17 | obtain a Kerberos Ticket. If you don't then the initial authentication |
| 18 | handshake may fail. |
| 19 | |
| 20 | When using NTLM, the user name can be specified simply as the user name, |
| 21 | without the domain, if there is a single domain and forest in your setup |
| 22 | for example. |
| 23 | |
| 24 | To specify the domain name use either Down-Level Logon Name or UPN (User |
| 25 | Principal Name) formats. For example, EXAMPLE\\user and user@example.com |
| 26 | respectively. |
| 27 | |
| 28 | If you use a Windows SSPI-enabled curl binary and perform Kerberos V5, |
| 29 | Negotiate, NTLM or Digest authentication then you can tell curl to select |
| 30 | the user name and password from your environment by specifying a single colon |
| 31 | with this option: "-u :". |
| 32 | |
| 33 | If this option is used several times, the last one will be used. |