From a387d881ecf1cfe8def1460fdf2faa3fdef66302 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 28 Nov 2016 01:01:13 +0100 Subject: cmdline-docs: more options converted and fixed Now all options are in the new system. --- docs/cmdline-opts/user.d | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 docs/cmdline-opts/user.d (limited to 'docs/cmdline-opts/user.d') diff --git a/docs/cmdline-opts/user.d b/docs/cmdline-opts/user.d new file mode 100644 index 000000000..439def348 --- /dev/null +++ b/docs/cmdline-opts/user.d @@ -0,0 +1,33 @@ +Long: user +Short: u +Arg: +Help: Server user and password +--- +Specify the user name and password to use for server authentication. Overrides +--netrc and --netrc-optional. + +If you simply specify the user name, curl will prompt for a password. + +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, +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 successfully +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, +Negotiate, NTLM or Digest authentication then you can tell curl to select +the user name and password from your environment by specifying a single colon +with this option: "-u :". + +If this option is used several times, the last one will be used. -- cgit v1.2.3