SSL Request process and questionnaire

Version 1

    Case response for SSL Requests

     

    I would be happy to assist with this. The process is outlined below. Please provide the info in BOLD so that I can generate a CSR that you can use to purchase a UCC certificate with.

     

    Adding SSL typically takes about a week. Here is a quick overview of the SSL process:

    1. Customer fills out the CSR (Certificate Signing Request) information.
    2. Jive forwards the CSR info to our hosting provider, and gets the CSR back (this takes a couple days).
    3. Customer takes the CSR from Jive and uses it to purchase a UCC certificate from a CA (Certificate Authority), then gives the certificate to Jive.
    4. Jive forwards the certificate to our hosting provider, who installs it on the load balancer.
    5. Any additional configuration options (such as redirects) are installed on the server.

     

    CSR Information

     

    QuestionCustomer Response
    How  would you like SSL configured? We can send all traffic over HTTPS, just logins and registrations, or make HTTPS optional.
    Common name (site's full domain name):
    Division (e.g., IT, Marketing):
    Organization (company name):
    Locality (e.g., city name):
    State or Province (fully spelled out):
    Email address for certificate (if desired):

    If you would like a specific *vanity URL for your UAT instance please specify here

    (otherwise we will append uat- to your existing URL to support SSL on your UAT site)


         *vanity URL= A web address or domain name created by a company in order to spread information about a particular product

                               A vanity URL should be unique, relevant and support your brand or message.

     

     

    UCC SSL Certificates and Customer DNS

     

    The typical SSL cert is configured with a Common Name (CN) of something like social.customer.com and Jive Hosting will ask the customer to configure a CNAME record in their DNS forsocial.customer.com to point to the hosted name of customer.hosted.jivesoftware.com.

     

    For Jive Apps Market Jive will have the customer create another DNS CNAME entry for apps.social.customer.com to point toapps.customer.hosted.jivesoftware.com.

     

    The best way to deal with this is the UCC SSL cert with a primary name of social.customer.com and aliases for UAT nodes.  This allows Jive to install one cert on all of the load balanced Virtual IPs and the customer has only one SSL cert to purchase and manage.

     

    This is an example DNS layout:

    PRODsocial.customer.comcustomer.hosted.jivesoftware.com
    PROD APPS MARKETapps.social.customer.comapps.customer.hosted.jivesoftware.com
    UATsocial-uat.customer.comcustomer.uat3.hosted.jivesoftware.com
    UAT APPS MARKETapps.social-uat.customer.comapps.customer.uat3.hosted.jivesoftware.com

     

    In the case above, Jive would ask the customer to create four DNS CNAME entries to point to the entries in column 3 as provided by Jive Hosting.