How can I configure Consumer Portal layout to work under secured (HTTPS) protocol?
In order to make Consumer Portal work under secured connections there are few additional configuration settings needed.
The Consumer Portal is a lightweight client application and thus requires a server backend service to provide necessary data and search services. There are two backend services used:
Those backend services use unsecured HTTP protocol by default and this will cause either mixed-content errors or service unavailable errors (depending on IIS settings) when HTTPS Consumer Portal tries to access them.
To fix this, make copies of the backend services under the secured web site, or simply make sure that you can access them through HTTPS.
This sample request can be used to check if the backend works with HTTPS: https://<server_address>/backend/v2/connection/setcookie
It should respond with a blank page and 200 OK status (e.g. when checking in browser developer console).
Please refer to attached screenshot showing a sample configuration.