Apache HTTPS Keys and Certificate Creation - Fluid Topics - 3.9 - Reference Guides

Fluid Topics Integration Guide

Product
Fluid Topics
Fluid Topics Version
3.9
Operating System
RHEL
Category
Reference Guides
Language
English
Target Audience
public

It is possible to define a custom URL for a tenant. The process involves an exchange between the customer and an Antidot representative as follows:

  1. The customer gets in touch with an Antidot representative to provide a custom URL, for example, https://documents.CUSTOMER.com.
  2. Based on this custom URL, Antidot generates a key on the server which hosts the portal.

    The following line shows how to generate a key for the doc.antidot.net domain name:
    • As root user

      openssl genrsa -out /etc/httpd/ssl/keys/doc.antidot.net.key 2048

  3. Antidot creates a Certificate Signing Request (CSR) in the appropriate directories.

    The following lines show how to generate the CSR for the doc.antidot.net domain name:
    • As root user

      openssl req -new -x509 -nodes -out /etc/httpd/ssl/cert/$GENERATED_CERTIFICATE.csr -keyout /etc/httpd/ssl/keys/doc.antidot.net.key

    • It is necessary to provide the following information:

      Country Name (2 letter code) [XX]: ${Country_Code}
      State or Province Name (full name) []:
      Locality Name (eg, city) [Default City]:${City}
      Organization Name (eg, company) [Default Company Ltd]:${Company}
      Organizational Unit Name (eg, section) []: ${Unit}
      Common Name (eg, your name or your server's hostname) []:<name>
      Email Address []:${Support_Mail}

  4. The customer purchases an SSL digital certificate with a bundle containing a signed SSL certificate chain and the CSR from a Certification Authority and sends it to an Antidot representative.
  5. Antidot installs the digital certificate (.crt file) and the bundle on the customer's server.
  6. The customer creates a DNS entry (CNAME) specifying that the custom URL is an alias for the final URL.