If you host with us
To use a custom domain, you will need to purchase an SSL certificate and supply it to us for installation.
We can on request supply you with a CSR, if we are given the following information:
Common Name: The fully-qualified domain name, or URL, you're securing.
If you are requesting a Wildcard certificate, add an asterisk (*) to the left of the common name where you want the wildcard, for example *.coolexample.com.
Organization: The legally-registered name for your business. If you are enrolling as an individual, enter the certificate requestor's name.
Organization Unit: If applicable, enter the DBA (doing business as) name.
City or Locality: Name of the city where your organization is registered/located. Do not abbreviate.
State or Province: Name of the state or province where your organization is located. Do not abbreviate.
Country: The two-letter International Organization for Standardization (ISO) format country code for where your organization is legally registered.
Once we have this information we will generate and supply you with a CSR file which you can use to purchase an SSL certificate. Please note we will need this for Apache Webserver.
While the primary responsibility for monitoring certificate renewals is with your IT team, we do also monitor these and if we haven't heard from you close to the expiry date - usually a few weeks before - we get in touch to discuss the process and request new files.
If we don't hear back from you and the expiry date is reached, an error message will be displayed to users trying to access your site. When this happens, we can temporarily move your Application to being accessible at our domain ( assetbank-server.com ) using our certificate to ensure consistent access to your application.
If you host Asset Bank On-Premise
Although it is possible to configure Tomcat itself to use SSL (and there is documentation available online about this), we recommend using a web server as the process of configuring IIS or Apache for SSL is well documented.
Asset Bank will work equally well with IIS or Apache - we recommend using whichever web server your IT team are most familiar with. We find that most clients using a Windows server use IIS, while those on Linux use Apache (IIS is Windows only!)