You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.
Before you upgrade make sure to read the General Upgrade instructions as well as the Upgrade instructions for previous versions.
The changes are color coded. Orange elements have been changed, Green elements have been added and Red elements have been removed compared to the 16.x release.
Table of contents
DCM Dashboard frontend reverse proxy
As opposed the default Blueriq Frontend the DCM Dashboard frontend needs to be run in a reverse proxy to guarantee that requests of the frontend reach the proper backing services. With release 16.6, we improved the DCM installation starter's reverse proxy (nginx) configuration by also supporting Blueriq forms applications.
Runtime location
The runtime location block of has been updated to also support Blueriq forms applications.
| Before | After |
|---|---|
location /runtime/ {
rewrite ^/runtime/([^/]*)/(server/)?(.*)$ /runtime/$1/server/$3 break;
proxy_pass http://gateway/;
}
| location /runtime/ {
rewrite "^/runtime/([a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}/)?(server/)?(.*)$" /runtime/$1server/$3 break;
proxy_pass http://gateway/;
}
|
Document Renderer Service
Make sure the password field has a noop or bcrypt password operation defined. When defining a bcrypt hashing operation you of course need to hash the password.
blueriq:
authentication:
username: blueriq
password: "{bcrypt}$2a$10$E/MZ1O2t/wU9TTCubVZgX.c6AFdFEUSYs7QJ.Ia2kyGd/msjEkERq"
blueriq:
authentication:
username: blueriq
password: "{noop}welcome"
Known issues
For an overview of known issue please refer to: Known issues.
Overview
Content Tools