○ Using a custom domain name with a secure SSL connection
If you like, you can set up your own URL instead of yourlearningenvironment.anewspring.com. Be aware that the aNewSpring app only works with a secure connection, so it will not be possible to log in with your own domain name that doesn't use HTTPS. See the solution in step 4.
1) Create a sub domain in your domain settings
This should always be a subdomain of an existing domain. If your own website is www.website.com, you could, for example, use elearning.website.com instead of yourlearningenvironment.anewspring.com.
2) Change the DNS settings of your domain.
The subdomain that you would like to use (elearning.website.com) should become a CNAME of yourlearningenvironment.anewspring.com. If you don't know how to set this up, the company that hosts your domain could help you with that.
If you use multiple subenvironments, it is very important to always use the standard aNewSpring URL as a CNAME in this way:
|aNewSpring URL||custom URL||CNAME|
If your custom URL has a different extension (.com, .nl, .co.za, etc.) than your aNewSpring URL, please contact us first. You might need to refer the CNAME to a different URL.
3) Notify us about your subdomain
Send us an email at email@example.com and let us know which URL you would like to use and for which subenvironment we should set this up. Due to our setup, you will be directed to the right subenvironment. This could also occur if you have set multiple subenvironments as the same CNAME.
4) Set up an SSL certificate (HTTPS)
Your new custom domain won't simply work with a secure SSL connection. SSL will encrypt sensitive information, so it can't be intercepted. You can recognise websites that use an SSL certificate by the presence of https in the link. Our aNewSpring app only works with a secure connection, so it will not be possible to log in with your own domain name if it doesn't use HTTPS. You can provide us with an SSL certificate that we will have installed by our hosting provider. To cover the costs, we charge USD 250 per installation. When a certificate expires, a new one will have to be purchased and installed on our server. To avoid the costs for the installation every year, you can also purchase a certificate that is valid for 3 years.
A) Generate a CSR
You will need a Certificate Signing Request (CSR) to request the certificate and the hosting provider of your domain will be able to help you with this.
If you use multiple subenvironments like in the example in step 2, it's best to purchase a Wildcard certificate. With this kind of certificate, all subdomains of, for example, *.website.com are covered. We would like to receive the SSL certificate with its private key (without a passphrase) in .crt, .ca-bundle or .pem format. We can then get it installed on our servers.
We arrange the certificate through SNI, and some old browsers don't support this. You will find more information about which browsers are supported on this website.
B) Purchase an SSL certificate and send it to us
If you use multiple subenvironments like in the example at step 2, it's best to purchase a Wildcard certificate. With this kind of certificate all subdomains of e.g. *.website.com are covered. We would like to receive the SSL certificate with its private key (without a passphrase) in .crt, .ca-bundle or .pem format. Next we can get it installed on our servers.
We arrange the certificate through SNI and some old browsers don't support this. You will find more information about which browsers are supported on this website.
WARNING: Certificates issued by the following companies are blocked in Google Chrome and Mozilla Firefox: Symantec, GeoTrust, Thawte, VeriSign, Equifax and RapidSSL.
Find more information here.
We advise you to purchase certificates from other companies.