HTTPS requires an SSL Certificate. When you generate an SSL Certificate,you are creating a keystore file and a keystore password for use when the browser interface connectsto the Master Server.
Crt and key files represent both parts of a certificate, key being the private key to the certificate and crt being the signed certificate. It's only one of the ways to generate certs, another way would be having both inside a pem file or another in a p12 container.
You can choose whether to have a Certifying Authority sign the certificateor you can use a self-signed certificate. A certificate signed by a CertifyingAuthority is trusted by browsers, therefore the browser does not issue a warningwhen a user connects to the browser interface on the Master Server. Generally, CertifyingAuthorities charge a fee to sign a certificate. A self-signed certificateis available for use immediately after you generate the certificate becauseyou do not have to wait for the Certifying Authority to sign it. However,a self-signed certificate is not trusted by the browser, so the browser issuesa warning each time a user connects to the Master Server.
To enable the browser interface to use SSL, you must first generate an SSL Certificate.You create a keystore file and a keystore password while you generate an SSLCertificate.
To create a keystore file and a keystore password you will use keytool. keytool is a security tool availablewith the JRE. If you do not have keytool installed, youmust install keytool before you can configure the provisioningsystem to use HTTPS. The N1 Service Provisioning System installs the JRE. If you are configuringHTTPS after you have installed the provisioning system, keytool isinstalled on the system.
Change to the directory in which you installed the JRE.
JAVA-HOME is the directory where you installedthe JRE. If you installed the JRE with the N1 Service Provisioning System 5.1, the JRE is installedin the N1SPS5.1-home/common/jre/bin directory.
Generate the certificate.
Set /keystore-location to the location andfilename of the keystore file where you want to store the generated key.
Set password to whatever passwordthat you want to use as the keystore password.
Follow the prompts to complete.
Do not include anypunctuation in the name of your organization, otherwise the Java Certificatetool fails when attempting to generate the request. The Common Name (CN)must be set to the fully qualified host name, including the domain name, componentof the URI.
If you want to use a Certificate signed by a Certifying Authority, followthis procedure to submit the Certificate to the Certifying Authority to besigned.
Generate the Certificate Request.
/keystore-location is the location and filenamewhere you stored the generated key.
Send the Certificate Request to the Certifying Authority.
Follow the instructions provided by the Certifying Authority. The CertifyingAuthority returns a Certificate Reply.
Save the Certificate Reply to a file.
Verify the Certificate Reply.
certificate-reply-file is the filename ofthe Certificate Reply that you received from the Certifying Authority.
Import the Certificate Reply file to the keystore file.
/keystore-location is the location and filenamewhere you stored the generated key. certificate-reply-file isthe filename of the Certificate Reply that you received from the CertifyingAuthority.
Verify the imported Certificate Reply.
/keystore-location is the location and filenamewhere you stored the generated key.
Important: This example is intended to provide general guidance to IT professionals who are experienced with SSL requirements and configuration. The procedure described in this article is just one of many available methods you can use to generate the required files. The process described here should be treated as an example and not as a recommendation.
When you configure Tableau Server to use Secure Sockets Layer (SSL) encryption, this helps ensure that access to the server is secure and that data sent between Tableau Server and Tableau Desktop is protected.
Looking for Tableau Server on Linux? See Example: SSL Certificate - Generate a Key and CSR.
Tableau Server uses Apache, which includes OpenSSL. You can use the OpenSSL toolkit to generate a key file and Certificate Signing Request (CSR) which can then be used to obtain a signed SSL certificate.
To configure Tableau Server to use SSL, you must have an SSL certificate. To obtain the SSL certificate, complete the steps:
You can find additional information on the SSL FAQ page on the Apache Software Foundation website.
Tableau Server allows SSL for multiple domains. To set up this environment, you need to modify the OpenSSL configuration file, openssl.conf, and configure a Subject Alternative Name (SAN) certificate on Tableau Server. See For SAN certificates: modify the OpenSSL configuration file below.
To avoid using the -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).
Open the Command Prompt as an administrator, and run the following command:
set OPENSSL_CONF=c:Program FilesTableauTableau Serverpackagesapache.<version_code>confopenssl.cnf
Notes:
When setting the Open SSL configuration environment variable, do not enclose the file path with quotation marks.
If you are using a 32-bit version of Tableau Server on a 64-bit computer, run the set OPENSSL_CONF=c:Program Files (x86)TableauTableau Serverpackagesapache.<version_code>confopenssl.cnf
command instead.
Generate a key file that you will use to generate a certificate signing request.
Open the Command Prompt as an administrator, and navigate to the Apache directory for Tableau Server. For example, run the following command:
cd C:Program FilesTableauTableau Serverpackagesapache.<version_code>bin
So the individuals are awaiting protection from Bitdefender’s updated version.
Run the following command to create the key file:
openssl.exe genrsa -out <yourcertname>.key 4096
Note: This command uses a 4096-bit length for the key. You should choose a bit length that is at least 2048 bits because communication encrypted with a shorter bit length is less secure. If a value is not provided, 512 bits is used.
Use the key file you created in the procedure above to generate the certificate signing request (CSR). You send the CSR to a certificate authority (CA) to obtain a signed certificate.
Important: If you want to configure a SAN certificate to use SSL for multiple domains, first complete the steps in For SAN certificates: modify the OpenSSL configuration file below, and then return to here to generate a CSR.
Run the following command to create a certificate signing request (CSR) file:
openssl.exe req -new -key yourcertname.key -out yourcertname.csr
If you did not set the OpenSSL configuration environment variable, OPENSSL_CONF
, you might see either of the following messages:
An error message about the config information being unable to load. In this case, retype the command above with the following parameter: -config .confopenssl.cnf
.
A warning that the /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.
To set an OpenSSL configuration environment variable, see Set the OpenSSL configuration environment variable (optional) section in this article.
When prompted, enter the required information.
Note: For Common Name, type the Tableau Server name. The Tableau Server name is the URL that will be used to reach the Tableau Server. For example, if you reach Tableau Server by typing 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.
Send the CSR to a commercial certificate authority (CA) to request the digital certificate. For information, see the Wikipedia article Certificate authority and any related articles that help you decide which CA to use.
When you have both the key and the certificate from the CA, you can configure Tableau Server to use SSL. For the steps, see Configure External SSL.
In a standard installation of OpenSSL, some features are not enabled by default. To use SSL with multiple domain names, before you generate the CSR, complete these steps to modify the openssl.cnf file.
Open Windows Explorer and browse to the Apache conf folder for Tableau Server.
For example: C:Program FilesTableauTableau Server<version_code>apacheconf
Open openssl.cnf in a text editor, and find the following line: req_extensions = v3_req
This line might be commented out with a hash sign (#) at the beginning of the line.
If the line is commented out, uncomment it by removing the # and space characters from the beginning of the line.
Move to the [ v3_req ] section of the file. The first few lines contain the following text:
# Extensions to add to a certificate request
basicConstraints = CA:FALSE
keyUsage = nonRepudiation, digitalSignature, keyEncipherment
After the keyUsage line, insert the following line:
subjectAltName = @alt_names
If you’re creating a self-signed SAN certificate, do the following to give the certificate permission to sign the certificate:
Add the cRLSign
and keyCertSign
to the keyUsage line so it looks like the following: keyUsage = nonRepudiation, digitalSignature, keyEncipherment, cRLSign, keyCertSign
After the keyUsage line, add the following line: subjectAltName = @alt_names
In the [alt_names] section, provide the domain names you want to use with SSL.
DNS.1 = [domain1]
DNS.2 = [domain2]
DNS.3 = [etc]
The following image shows the results highlighted, with placeholder text that you would replace with your domain names.
Save and close the file.
You can generate a private cryptographic key and optionally a self-signed certificate. The certificate signing request (CSR) that is needed by the certificate authority (CA) is created by default. You can generate an RSA key or ECDSA key. If you generate an RSA key, you must define the key length and the hash algorithm of the generated RSA keys. Crypto key generate rsa RSAkeysmaybegeneratedonaconfiguredandavailableUSBtoken,bytheuseoftheondevicename: keywordandargument.KeysthatresideonaUSBtokenaresavedtopersistenttokenstoragewhentheyare. Create Your Own Cryptogram! If you enter a phrase into the text box below, our machines will encrypt it for you and you can send it to a friend! Give it a shot (limited to 255 characters). Can a cryptogram generate keys. This application derives session keys from the card master key, following the algorithm described in EMV 4.1, Book 2, Part III, Annex A1.3. Optionally it can generate application cryptograms (ARQC, TC, AAC, AAR), when given the input the the Generate Application Cryptogram command, and the internal configuration of the card.
Complete the steps in Create a certificate signing request to send to a certificate authority section, above.
If you prefer to use a different version of OpenSSL, you can download it from Open SSL for Windows.