...
Step 3: When the configuration tasks have been created for every server, these tasks have to be applied . The configuration tasks have to been applied for each serverson each server. After applying the new configuration values has been pushed to the local registry and the services reread the new values and started to work based on the new values.
The configuration passwords are stored in an encrypted format in the central database and the registry too. Contrary to the other entities the passwords are handled in a different way in the server configuration related endpoints. Numerous integrations require a connection string in a complex format instead of dedicated configuration values. These connection strings contain the passwords in an encrypted format with unencrypted configuration values separated with separator characters in one configuration value. Based on that at the backend side the automatic password encryption is not possible. Due to that the passwords have to been encrypted by the client with usage of the dedicated password encryption endpoint.
Another difference between the server configuration related endpoints and the other aforementioned introduced endpoints is the password verification. As a result of the complex connection string format there is no password verification action in these endpoints. The encrypted values can be retrieved by the client.
Server configuration examples
The following sections different use case examples demonstrates the usage of the server configuration related endpoints.
Individual server configuration modification
Due to the server configurations are stored in two different location: central database and registry values, the current configuration values can be retrieved from both location.