Skip to content
← Ideas and Feedback

Have an idea for a new feature?

Ideas and Feedback: Customer Portal & Knowledge Base

Categories

(thinking…)

Custom SSL or LetsEncrypt SSL to allow https on custom domains in the customer portal

205 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Andrew Oliver shared this idea  ·   ·  Report…  ·  Admin →
Released  ·  AdminYakov Gorbulsky (Product Manager, Atera) responded  · 

Hey all, 


I am happy to announce Atera has introduced the support for custom urls with a secure HTTPs connection by generating CNAME records for the Customer Portal.


By completeing the process, your portal will be covered by unique certificates under the DigiCert umbrella.

Moreover, Atera will automatically renew the certificate for you so there is no need for anything on your end beyond the initial setup.


Feel free to read more about the feature here: https://support.atera.com/hc/en-us/articles/360000689808-Set-up-SSL-for-your-Customer-Portal


To enable the feature, reach out to your account manager or the customer success team via success@atera.com 


All the best,

Yakov

Show previous admin responses (1)

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Charles Hanekom commented  ·   ·  Report

    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.

  • Andrew commented  ·   ·  Report

    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!

  • Andrew commented  ·   ·  Report

    Or at least have Atera's back end generate one using free LetsEncrypt SSL certificates. Pretty easy to implement.

  • nick fothergill commented  ·   ·  Report

    This is so important. If not its installing from non branded URLs or worse a http link

  • Simon Ainsworth commented  ·   ·  Report

    It would be great if we could upload our own certificate so customers can see portal.customername.com and still use SSL.

  • Timothy Walker commented  ·   ·  Report

    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 MSPs won't want to use a non-branded URL for their clients !

  • support commented  ·   ·  Report

    Support SSL on custom domains. Even if it's a more complicated configuration or that we need to upload the certificates ourselves. You have white-labeling listed as a feature of your product, this is something that would be required if you want to claim to offer that feature. Thanks in advance!

  • alf commented  ·   ·  Report

    Please implement SSL for whitelabeled domains on the customer portal: e.g. support.customerdomain.com, this is crucial to protect any and all customer data which is being entered into the new ticket form when the customer press create new ticket. Both Firefox and Chrome now actively blocks and warns users against non-HTTPS/SSL webpages, so this is really important to not having customers doubt your MSP's credibility and knowledge about web security. Thank you.

  • Pronet Support commented  ·   ·  Report

    I would like to have my technicians log in to my own CNAME for the support system. My technicians would log in to support.domain rather than app.atera.com This was the control panel is also white labelled and my staff/sales team could show potential clients reports and other advanced features without giving away the product that we are using in order to provide these features. I have no issue even buying a 3rd party SSL to secure that CNAME record. Potentially run an iframe or something

  • it.notify commented  ·   ·  Report

    Lets make the customer portal use SSL. Customers would like to upload sensitive documents using the portal but, currently the site is not secure. This is critical!

  • Thomas Schreiner commented  ·   ·  Report

    The customer portal does not support SSL.  In 2021 this should be a must!

  • Patrick Veldboer commented  ·   ·  Report

    Adding your own SSL certificate to the customer portal. nowadays its not a great plan to instruct customers to enter a webpage which had SSL security warnings. we would like to use the personal branding. but letting customers ignore an security warning isn't the right advice for an MSP

  • d.vanbeek commented  ·   ·  Report

    SSL on Customer Facting Portal with own URL. So https://support.owndomain.com rather than https://clientname.atera.com. We have several wholesale partners that provide this level of whitelabeling. If not possible, it would be a nice alternative to have a set of standard PHP files that could be self hosted and connects to Atera Client Facing Portal.

  • info commented  ·   ·  Report

    Disable NON-SSL connections to customer portal: offering a non-ssl customer portal and allowing data transmission over unencrypted channels is a clear signal for bad security by design (Product owner, I have also other critical security issues, feel free to contact me). In any case, you do not want to establish an image for bad security - neither for Atera, nor for your MSP customers.

2 Next →