The latest Sprint 2020.26 bring us a new version 2.1 of Design Room ONE available for HCL RTist users. In this new version authentication functionality has been significantly improved and lost its EXPERIMENTAL tag. One of the improvements includes refactoring the way the Design Room ONE server integrates with Keycloak for authentication. As a result, the configuration procedure is now easier: all the settings that need to be updated are now located in Design Room ONE’s main configuration file – server-config.json. Due to these improvements, there is now no need for Design Room ONE to store a Keycloak administrator key making this integration even safer, since Design Room ONE server would only be able to access pieces of Keycloak information it needs to manage access to its designs. You can refer to Authentication Setup for detailed instruction on migrating Keycloak realms configured with previous versions of Design Room ONE without loosing any information about users and their roles. Another update related to server configuration is the introduction of a single property dr_db_url controlling database connection — provides more flexibility and allows using password protected databases, which are standard in cloud environments like Azure or AWS. This is since version 2.1 Design Room ONE supports integration with Collaborative Lifecycle Management (CLM) tools version 6.0.6.1. If you are using CLM tools to track your requirements with CLM 6.0.6.1 (read System Requirements for the full list of supported versions and other requirements) you would be able to create “Derived From” links in your modeling tool e.g. HCL RTist from a model element to a requirement. These links will be visible in Design Room ONE after the model has been exported to the server. After that matching “Derives Architecture Element” links will be visible in your requirements management application and you would be able...

During several last sprints, the Design Room ONE team has been working on various improvements and enhancements in Authentication functionality. The latest Design Room ONE 2.0 2020.16, which is a part of HCL RTist, brings multiple important updates. First, we simplified the installation and configuration procedure significantly by introducing Docker support. Now, with a fewer commands, users can get Keycloak, NodeJS, Mongo running and connected, watch the demo video or check the detailed instruction on GitHub to learn more. Second, authentication is no longer blocking running reports against models published on the Design Room ONE server; updated instructions cover the necessary configuration steps. Before running a report, a user needs to enable Basic authentication scheme in Design Room ONE server settings, and after that provide necessary credentials when configuring the Data Source in the reporting tool, as shown below.     Third, automated publishing scenarios, when for example a new version of the model gets published to server each time it is updated in the repository now also support authentication. Two new attributes user and password were introduced to specify the credentials to be used during automated publishing process. And finally, multiple improvements were made to publishing wizard. If the Allow insecure connection checkbox is checked, it will also permit communication with Keycloak server, even if its HTTPS certificate cannot be verified, this comes handy for example when the default self-signed certificate is used in Keycloak deployment. Another improvement can be observed when connecting to a Design Room ONE server takes noticeable time, e.g. because of network delays. Now users are notified on the operation being performed in the header section of the Export wizard window.   Stay up-to-date with all our releases and features by checking out our blog.