You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
It is recommended to enable HTTPS to encrypt communication with the Studio server. This includes communication with Encore and the management service which is used by the Publisher, Development Dashboard, and the Blueriq Model Analyzer (BMA).
Technical knowledge assumed
This step-by-step guide on HTTPS configuration and implementation assumes a foundational understanding of web security, networking, and server administration. The instructions provided are intended for individuals with technical expertise in these areas.
In this step-by-step example we use self signed certificate. However, it is recommended to use a certificate that is issued by a Certificate Authority (CA).
Enabeling HTTPS also enables 'copy from clipboard' functionalities in Blueriq Encore.
Option 1: Enable HTTPS in the default Internet Information Services (IIS)
- Go to Internet Information Services (IIS) Manager.
- Select the Blueriq site and from the context menu, open the Bindings... dialog:
- Add a new binding with type 'HTTPS' and select the certificate you want to use.
- Click on 'View' to check the 'Issued to' property of the certificate. In a real situation, the 'Issued to' field should be the host of your Blueriq deployment instead of localhost:
- Now select OK in both the 'Certificate' and 'Add Site Binding' dialog.
- It is recommended but not required to remove any site binding of type 'HTTP' from the list of site bindings.
- To use HTTPS, go to the 'Issued to' host from step 4, using the https scheme. In this example, that is https://localhost/.
- The URL for user management in Keycloak will be: https://localhost/Keycloak/admin/master/console/#/BlueriqStudio17 for Blueriq 17
Establishing a connection from the development dashboard to the Studio server
Now that the URL of the managment service has changed, the blueriq.studio.url property needs to be updated in the application-development-tools.properties file in the conf folder of the runtime.
There are two options:
- use https://localhost/Studio/Server/Services/ManagementService
If you are using a self signed certificate, you will have to add this certificate to the jave truststore as explained here: Security: HTTPS [editor]
- use the internal port if the runtime is deployed on the same server as the Studio server (http://localhost:17093/Services/ManagementService for Blueriq 17)
Option 2: HTTPS reverse proxy server
Instead of changing the settings in the default IIS instance to enable HTTPS, you could use a reverse proxy server.
Please refer to these page to configure the Runtime behind a reverse proxy server: Using a reverse proxy server
Overview
Content Tools