From 8bbc0f15a7609736a7fa2fe19bf12068b5dbea64 Mon Sep 17 00:00:00 2001 From: Marko Stojanovic Date: Tue, 20 Feb 2024 12:56:37 +0100 Subject: [PATCH] Update documentation --- doc/TRUEConnector/prerequisite.md | 4 ++-- doc/selfDescriptionAPI/changepassword.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/TRUEConnector/prerequisite.md b/doc/TRUEConnector/prerequisite.md index 7dea108..a07b378 100644 --- a/doc/TRUEConnector/prerequisite.md +++ b/doc/TRUEConnector/prerequisite.md @@ -139,11 +139,11 @@ By regularly updating SSH keys every three months, administrators will enhance t ## Secure DB -It's mandatory to set **AES256-SECRET-KEY** which is valid password for column encryption with AES256 algorithm. +It's mandatory to set **AES256-SECRET-KEY** as OS variable which is valid password for column encryption with AES256 algorithm. ## Post configuration steps -Once TRUE Connector is successfully configured and is up and running, responsible user for setting up environment and configuring connector should generate new passwords for 2 type of users required for operating with connector. More information how to do this can be found [here](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/blob/1.14.8/doc/SECURITY.md#change-default-password). +Once TRUE Connector is successfully configured and is up and running, responsible user for setting up environment and configuring connector should change existing TRUE Connector users, more information about user management can be found here [here](../user_management.md). Make sure to update following properties to address your usecase: diff --git a/doc/selfDescriptionAPI/changepassword.md b/doc/selfDescriptionAPI/changepassword.md index 070f7eb..29b0ed1 100644 --- a/doc/selfDescriptionAPI/changepassword.md +++ b/doc/selfDescriptionAPI/changepassword.md @@ -3,7 +3,7 @@ If you want to change password for connector users, this can be done via following endpoint ``` -/notification/password/{new_password} +/api/password/{new_password} ``` Using this endpoint, it is guaranteed that the password strength rules configured in the `application.properties` file will be enforced.