Studio

User Management

When running the installer to install Blueriq Studio, 3 users are created:

• admin
• administrationpage
• runtime
  
  

Please make sure to change the default password during installation.

After the typical / custom installation the users are stored locally. Although the credentials are encrypted within Studio, it is advisable to authenticate against an Active Directory instead. This way managing users is done outside Blueriq and you have more control over password and lockout policies. Also the passwords are stored in the Active Directory and not within Studio.

To install or change Blueriq Studio security and user management, please read this article: Studio Security Modes. 

Securing the administation page

During installation of Studio, an administration console is also installed. Via this console it is possible to download or upload a Studio repository. The Studio repository contains the models and business logic so it is advisable to secure this console. This is done by following the steps in this article: Studio.

Encrypting a project export

In Studio, it is possible to export a project (.zip file) which can be deployed to the Blueriq Runtime (Export a project. It's advisable to check the "Encrypt" box before exporting so the .zip file does not contain the application model in plain text. Instead of exporting project manually, Blueriq also provides an application called Blueriq Publisher which automates the distribution of applications over environments.

Studio over HTTPS

IIS can be configured to acces Studio and the Studio Management Service over HTTPS. 

1. Open Internet Information Services (IIS) Manager on the site where Blueriq is installed. 
2. Select the Blueriq site and from the context menu, open the Bindings... dialog:
   
   
   
3. Add a new binding of type 'HTTPS' and select the certificate you want to use. In this example, we use a self signed certificate, which is not recommended on a production environment.
   
   
   
4. 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:
   
   
   
5. Now select OK in both the 'Certificate' and 'Add Site Binding' dialog.
6. It is recommended but not required to remove any site binding of type 'HTTP' from the list of site bindings.
7. To use HTTPS, go to the 'Issued to' host from step 4, using the https scheme. In this example, that is https://localhost/.