johnmcdraper's avatar
johnmcdraper
Occasional Contributor
7 years ago
Status:
New Idea

Server should handle HTTPS as part of delivered product

SB has a nice HELP page on how to get certificates and configure your SmartBear server to use secure HTTPS rather than HTTP.

 

With both FF and Chrome now giving warnings when any password web page is not HTTPS, it's becoming a pain to field calls asking if their reviews are secure.  

 

Given the world is heading towards all pages being secure, SmartBear should consider delivering Collaborator with certificates so a secure https server would now be the default installation, rather than require IT departments to do more work...

1 Comment

Sort By
  • jh's avatar
    jh
    New Contributor
    6 years ago

    The problem is that the installer would need to generate self signed certificates on demand (to match your installed domain name). The end user experience would then be worse: instead of "Not secure" being displayed in the bar at the top, you will get big, scary, full screen security warning and then have to click the small grey link to say, yes, you do trust the site.