Another important change is our move to require HTTPS protocol for all users on the new user interface. In 2016 Google announced plans to mark web pages (such as the new ClickHome interface) as Not Secure if they are not using HTTPS (see links here and here). This also applies to the backend (see here), so the ClickHome Web Services will need to be installed on a web server with an SSL certificate for HTTPS access.
The API implemented in ClickHome Web Services exposes existing functionality, so we are not rewriting the entire application, but just providing a new way of accessing it. This means that we can rapidly implement the new user interface based on this API and deliver regular updates and respond quickly to user feedback and suggestions. To facilitate this, we will be hosting the user interface so that there is no need for your IT team to schedule downtime and install the software for users to access the latest versions. This might seem strange at first with potential problems, but we’ve covered a lot of this in our planning as shown below, and our team are happy to discuss any other concerns you may have. The key points to this are:
- We host this content on Amazon behind a Cloudfront content delivery network which has edge locations in Sydney, Melbourne and Perth.
- We keep all versions of the user interface online so if there is any issue, we can roll users back to a previous version at any time.
- All your data is still stored in your existing ClickHome database.
- Users get the new version when they refresh the page or log out and log back in.
- All links such as direct links to contracts, saved searches etc. automatically redirect to the version that the user is logged in with.
- By default, the version of the user interface will be based on the version of ClickHome installed on your server.
- As a last resort, your IT team can request that your site be locked to a specific version of the user interface.
- If you stay on older versions of ClickHome on the Server, then when we release new versions of the user interface that only work with newer versions, your users will stay on the last version of the user interface for that server version.
- We will deploy and test new versions of the user interface before making it available to end users.
- Most importantly, the user interface is downloaded by your users into your browser and runs on your computers. The security impact of this is that it is effectively the same security setup as you have with the Silverlight interface with your data transmitted between your users’ computers and your servers, and not through our servers or networks.
The below graphic illustrates how our new user interface works and can be enlarged by clicking on the image.
- Microsoft Edge
Other browsers should work as we use many tools developed to support other browsers, and compared to Microsoft's approach with Internet Explorer, the developers of these browsers are very focused on compatibility with agreed standards.