Custom SSL or LetsEncrypt SSL to allow https on custom domains in the customer portal
Nice! The feature you requested is being considered for development. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
Bram Dispa commented
Most of my clients actively block non-HTTPS websites. The non-branded URL looks unprofessional, so at the moment I'm sticking to an external solution. I'd rather have all my MSP elements in one place, so I'm looking forward to seeing this feature added soon. Let's Encrypt is just fine for this application.
I've been using Atlassian JIRA / ServiceDesk a few years and they were not able to implement custom domains for more than 11 years:
I am still new to Atera but you've already surprised me a few times with your quick development.
This is your turn to do it again :)
Michael Cain commented
HTTPS on a login page is absolute must have.
Simon Holt commented
Desperately need this feature. Please implement ASAP. Thanks
Ryan Foster commented
With all the heightened awareness concerning cybersecurity, I think this needs to be investigated and implemented ASAP! HTTP should not even be an option for a platform such as this.
Loris Delorenzi commented
Would be sooo nice..
Charles Hanekom commented
We are also confronted with this issue. A client just emailed us stating that the site looks unsecure. Luckily he has the knowledge to proceed anyway, but this looks very bad for us as a company. The white label feature was one of the reasons we were so keen to use this product so it would be really great if we can add an SLL Certificate or it be added for custom URL's as well from Atera's side.
I am shocked that this isn't implemented, or at the very least a priority.
Not only does it detract from the advertised whitelabel services Atera promises, but looks unprofessional to the customer and raises security concerns whenever they try to access it.
LetsEncryptSSL API is so easy to use and implement there's really no excuses!
nick fothergill commented
This is so important. If not its installing from non branded URLs or worse a http link
Timothy Walker commented
This is an essential component that is missing.
No system should ever allow you to enter credentials via a non-https page. Using https://<companyname>.servicedesk.atera.com works but I imagine most clients won't want to use a non-branded URL for their clients !