< > ~ ! @ # $ % ^ * / ( ) ? . , &
Field | Explanation | Example |
---|---|---|
Common Name | The fully qualified domain name to which the certificate applies. The domain names example.com and www.example.com are distinct from each other, so be sure to submit your request for the right domain. If you are purchasing a wildcard certificate, use *.example.com. | example.com |
Organization Name | The exact legal name of your organization. The Certificate Authority (CA) might seek to confirm that your organization is real and legally registered, so don’t abbreviate words that aren’t abbreviated in the organization’s legal name. | Example Inc. |
Organizational Unit | The branch of your organization that is making the request. | Marketing |
City/locality | The city where your organization is legally located. Do not abbreviate the city name. | San Antonio |
State/province | The state or province where your organization is legally located. Do not abbreviate the state or province name. | Texas |
Country/region | The two-letter International Standards Organization (ISO) abbreviation for your country. | US |
Field | Explanation | Example |
---|---|---|
Common Name | The fully qualified domain name to which the certificate applies. The domain names example.com and www.example.com are distinct from each other, so be sure to submit your request for the right domain. If you are purchasing a wildcard certificate, use *.example.com. | example.com |
Organization Name | The exact legal name of your organization. The CA might seek to confirm that your organization is real and legally registered, so don’t abbreviate words that aren’t abbreviated in the organization’s legal name. | Example Inc. |
Organizational Unit | The branch of your organization that is making the request. | Marketing |
City/locality | The city where your organization is legally located. Do not abbreviate the city name. | San Antonio |
State/province | The state or province where your organization is legally located. Do not abbreviate the state or province name. | Texas |
Country/region | The two-letter ISO abbreviation for your country. | US |
Field | Explanation | Example |
---|---|---|
Domain Name | The fully qualified domain name to which the certificate applies. The domain names example.com and www.example.com are distinct from each other, so be sure to submit your request for the right domain. If you want to secure both domains, you can use the Alt Names field. If you are purchasing a wildcard certificate, use *.example.com. | example.com |
Alt Names | (Optional) Additional domains that you want to add to the request. Each CA treats these differently, and the CA might charge for additional names. You can submit a comma-separated list. | www.example.com, secure.example.com |
Email Address | (Optional) A contact email address for the certificate. | [email protected] |
Organization Name | The exact legal name of your organization. The CA might seek to confirm that your organization is real and legally registered, so don’t abbreviate words that aren’t abbreviated in the organization’s legal name. | Example Inc. |
Organizational Unit | (Optional) The branch of your organization that is making the request. | Marketing |
City | The city where your organization is legally located. Do not abbreviate the city name. | San Antonio |
State or Province | The state or province where your organization is legally located. Do not abbreviate the state or province name. | Texas |
Country | Choose your country from the drop-down menu. The two-letter ISO abbreviation for your country is included in the CSR. | United States |
Private Key Bit Length | Key sizes smaller than 2048 are considered insecure and might not be accepted by a CA. | 1024,2048,4096 |
Hashing Algorithm | Both algorithms are currently trusted in mainstream browsers and offer industry recommended security. SHA-512 requires additional CPU processing. | SHA-256, SHA-512 |
< > ~ ! @ # $ % ^ * / ( ) ? . , &
Field | Explanation | Example |
---|---|---|
Device(s) | The server or servers for which you want to generate a CSR. Use the drop-down menu to select your servers. | |
Common Name | The fully qualified domain name to which the certificate applies. The domain names example.com and www.example.com are distinct from each other, so be sure to submit your request for the right domain. If you want to secure both domains, you can use the Alt Names field. If you are purchasing a wildcard certificate, use *.example.com. | example.com |
Alt. Names | (Optional) Additional domains that you want to add to the request. Each CA treats these differently, and the CA might charge for additional names. You can submit a comma-separated list. | www.example.com, secure.example.com |
Email Address | (Optional) A contact email address for the certificate. | [email protected] |
Organization | The exact legal name of your organization. The CA might seek to confirm that your organization is real and legally registered, so don’t abbreviate words that aren’t abbreviated in the organization’s legal name. | Example Inc. |
Organizational Unit | (Optional) The branch of your organization that is making the request. | Marketing |
Locality (City) | The city where your organization is legally located. Do not abbreviate the city name. | San Antonio |
State or Province Name | The state or province where your organization is legally located. Do not abbreviate the state or province name. | Texas |
Country | Choose your country from the drop-down menu. The two-letter ISO abbreviation for your country is included in the CSR. | United States |
-config
argument with every use of openssl.exe, you can use the OPENSSL_CONF
environment variable to ensure that the correct configuration file is used and all configuration changes made in subsequent procedures in this article produce expected results (for example, you must set the environment variable to add a SAN to your certificate).set OPENSSL_CONF=c:Program FilesTableauTableau Serverpackagesapache.<version_code>confopenssl.cnf
set OPENSSL_CONF=c:Program Files (x86)TableauTableau Serverpackagesapache.<version_code>confopenssl.cnf
command instead. cd C:Program FilesTableauTableau Serverpackagesapache.<version_code>bin
openssl.exe genrsa -out <yourcertname>.key 4096
openssl.exe req -new -key yourcertname.key -out yourcertname.csr
OPENSSL_CONF
, you might see either of the following messages:-config .confopenssl.cnf
./usr/local/ssl
directory cannot be found. This directory does not exist on Windows, and you can simply ignore this message. The file is created successfully.tableau.example.com
in the address bar of your browser, then tableau.example.com
is the common name. If the common name does not resolve to the server name, errors will occur when a browser or Tableau Desktop tries to connect to Tableau Server.C:Program FilesTableauTableau Server<version_code>apacheconf
req_extensions = v3_req
# Extensions to add to a certificate request
basicConstraints = CA:FALSE
keyUsage = nonRepudiation, digitalSignature, keyEncipherment
subjectAltName = @alt_names
cRLSign
and keyCertSign
to the keyUsage line so it looks like the following: keyUsage = nonRepudiation, digitalSignature, keyEncipherment, cRLSign, keyCertSign
subjectAltName = @alt_names
DNS.1 = [domain1]
DNS.2 = [domain2]
DNS.3 = [etc]