To request a Custom URL, Subdomain or SSL renewals, please submit a support ticket in support ticket feature within the platform. Attach the following files to the ticket:
The CSR, Private Key and SSL Certificate (.crt,. chain and .key files)
Name of requested domain or subdomain: _____________________________________________
Your Primary Domain: _____________________________________________________________
An example of the four files required to process your Custom URL request is shown below.
cloud.disney.req (or.cloud.disney.csr)
cloud.disney.crt
cloud.disney.chain
cloud.disney.key
Important! Your request will be delayed if there are any problems, missing, incomplete, or mismatched SSL certificate files. The SSL digital certificate authenticates a website's identity for our servers to be able to establish encrypted conversations. Please note: Self-signed certificates will not be accepted since they are not verified by a certificate authority (CA)
You can use an online CSR & Key Generator or Wizard, such as https://decoder.link/csr_generator or https://csrgenerator.com If you are not able to generate a CSR, certificate, and Private Key file for the desired subdomain, please ask your website Host provider to create the files for you. If you were able to create the files, please submit them to your host provider (example: Namecheap or GoDaddy) to create the SSL Certificate files.
Here's a link to a video tutorial: How to create a CSR, Private Key and Certificate File
Important: If your SSL provider requests server details, make sure the certificate type is for Apache/Nginx servers. Please share 35.231.84.10 if an IP address is necessary. The subdomain/custom URLs will be hosted by TD SYNNEX/Tech Data; therefore, inform your SSL provider that hosting services are not required. Also, do not pay for costly SSL or Wildcard SSL certificates. If you have a Wildcard SSL certificate on your primary domain, Engineering will consider accepting it if you supply your Private Key. (This is not advised.) The SSL certificate will be installed on our servers, not your servers or your host provider's servers, by the TD SYNNEX/Tech Data Engineering team.
Create the CNAME Records:
Please create the CNAME records in your DNS or Host provider, pointing your custom URL to catalog.ses.techdata.com.
Example: CNAME cloud.disney.com points to catalog.ses.techdata.com
Please read the links below for more information or contact your SSL provider if you have any questions about CSRs, Private Keys, or SSL certificates.
CSR (Certificate Signing Request)
A CSR is an encoded file that provides you with a standardized way to send DigiCert your public key as well as some information that identifies your company and domain name. When you generate a CSR, most server software asks for the following information: common name (e.g., www.example.com), organization name and location (country, state/province, city/town), key type (typically RSA), and key size (2048-bit minimum). CSRs are used in the process of public key cryptography, which is used to validate identities on the Internet. A requestor could use tools like a CSR Generator to create the CSR and Key files but be sure to send the files to an SSL provider like Go Daddy to create the SSL certificate file.
REQ Files
A REQ file is a file used in the process of setting up a digital certificate. It stores a Certificate Signing Request (CSR), which includes information that uniquely identifies the initiator of the request. REQ files are sent to trusted entities (certificate authorities) who use the requests to generate valid digital certificates for the requesters. The “.key” file is required for Engineering to install the SSL certificate on the server.
What is contained in a CSR?
Common Name: The FQDN (fully qualified domain name) you want to secure with the certificate (Examples: secure.website.org, *.domain.net, cloud.bestcloudreseller.com).
Organization: The full legal name of your organization, including the corporate identifier.
Organization Unit (OU): Your department, such as ‘Information Technology’ or ‘Website Security.’
City or Locality: The locality or city where your organization is legally incorporated. Do not abbreviate.
State or Province: The state or province where your organization is legally incorporated. Do not abbreviate.
Country: The official two-letter country code (i.e., US, CH) where your organization is legally incorporated.
Here's an example of a CSR Generator - https://decoder.link/csr_generator
Certificate Authority (CA)
If you have the required files, now it's time to forward them to a certificate authority (CA), which can be your primary domain hosting service or SSL provider, such as Go Daddy. A certificate authority (CA) is an entity that is trusted to sign, issue, distribute and revoke digital certificates. Most digital certificates serve two main functions:
1. It verifies the identity of the applicant. With digital certificates, you can be sure that the entities (websites, companies, individuals, etc.) with whom you are interacting are really who they say they are. It binds a public key to an entity.
2. It encrypts the data transferred between two systems so that only the intended receiver can decipher it.
SSL Certificates
An SSL certificate, or secure certificate, is a file installed on a secure Web server (TD SYNNEX/Tech Data's server in this instance) that identifies a website. This digital certificate establishes the identity and authenticity of the company or merchant so that online shoppers can trust that the website is secure and reliable. A third party, such as Verisign or Thawte, verifies the companies and their websites to ensure that they are legitimate (they are who they claim to be).
Because digital certificates verify a company's authenticity, they do not last indefinitely. SSL certificates are typically valid for one to three years. If the certificate is not renewed in time, you may see an alert box pop up that says, "This website's certificate has expired."
*Please note: Self-signed certificates are not accepted. * A self-signed certificate is one that has been signed by an individual's private key rather than a certificate authority that is widely trusted (CA). Self-signed certificates or certificates issued by private CAs are not suitable for use with the public, and because the certificate has not been validated by a third party, visitors to your customer portal will see a browser warning that the certificate should not be trusted; as a result, we cannot accept self-signed certificates.
Please attach all 3 files to the StreamOne Ion Support ticket. Please allow up to four weeks for the custom URL creation or renewal to be completed. When your subdomain is ready, you will be contacted via Support Ticket. Any defects, missing files, or mismatches in the SSL certificate files can cause your request to be delayed.
To submit a support request, in StreamOne Ion, click the "?" icon in the upper right menu bar or click the Support button in the menu. Alternatively, you can click Submit a ticket in the Knowledge Base. Fill out all mandatory fields, or read How to Use StreamOne Freshdesk to Submit and View Support Tickets for more information.