73 lines
2.2 KiB
Groff
73 lines
2.2 KiB
Groff
|
|
.\" generated by cd2nroff 0.1 from CURLOPT_USERNAME.md
|
||
|
|
.TH CURLOPT_USERNAME 3 "2025-07-07" libcurl
|
||
|
|
.SH NAME
|
||
|
|
CURLOPT_USERNAME \- username to use in authentication
|
||
|
|
.SH SYNOPSIS
|
||
|
|
.nf
|
||
|
|
#include <curl/curl.h>
|
||
|
|
|
||
|
|
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_USERNAME,
|
||
|
|
char *username);
|
||
|
|
.fi
|
||
|
|
.SH DESCRIPTION
|
||
|
|
Pass a char pointer as parameter, which should be pointing to the
|
||
|
|
null\-terminated username to use for the transfer.
|
||
|
|
|
||
|
|
\fICURLOPT_USERNAME(3)\fP sets the username to be used in protocol
|
||
|
|
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 do not then the initial part of the authentication
|
||
|
|
handshake may fail.
|
||
|
|
|
||
|
|
When using NTLM, the username can be specified simply as the username 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, \fBEXAMPLE\user\fP and
|
||
|
|
\fBuser@example.com\fP 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 username, use the
|
||
|
|
\fICURLOPT_PASSWORD(3)\fP and \fICURLOPT_LOGIN_OPTIONS(3)\fP options.
|
||
|
|
|
||
|
|
The application does not have to keep the string around after setting this
|
||
|
|
option.
|
||
|
|
.SH DEFAULT
|
||
|
|
blank
|
||
|
|
.SH PROTOCOLS
|
||
|
|
This functionality affects all supported protocols
|
||
|
|
.SH EXAMPLE
|
||
|
|
.nf
|
||
|
|
int main(void)
|
||
|
|
{
|
||
|
|
CURL *curl = curl_easy_init();
|
||
|
|
if(curl) {
|
||
|
|
CURLcode res;
|
||
|
|
curl_easy_setopt(curl, CURLOPT_URL, "https://example.com/foo.bin");
|
||
|
|
|
||
|
|
curl_easy_setopt(curl, CURLOPT_USERNAME, "clark");
|
||
|
|
|
||
|
|
res = curl_easy_perform(curl);
|
||
|
|
|
||
|
|
curl_easy_cleanup(curl);
|
||
|
|
}
|
||
|
|
}
|
||
|
|
.fi
|
||
|
|
.SH AVAILABILITY
|
||
|
|
Added in curl 7.19.1
|
||
|
|
.SH RETURN VALUE
|
||
|
|
\fIcurl_easy_setopt(3)\fP returns a CURLcode indicating success or error.
|
||
|
|
|
||
|
|
CURLE_OK (0) means everything was OK, non\-zero means an error occurred, see
|
||
|
|
\fIlibcurl\-errors(3)\fP.
|
||
|
|
.SH SEE ALSO
|
||
|
|
.BR CURLOPT_HTTPAUTH (3),
|
||
|
|
.BR CURLOPT_PASSWORD (3),
|
||
|
|
.BR CURLOPT_PROXYAUTH (3),
|
||
|
|
.BR CURLOPT_USERPWD (3)
|