You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The global configurations ldap.truststore.password and ldap.truststore used for enabling the SSL/TLS support for LDAP i.e LDAPS are set type dynamic and it is expected that updating them do not require cloudstack-management service restart. However this is the current behaviour.
On setting the value for the above parameters for the first time it works without a restart.
If you update it later on it requires service restart. There is no message returned to admin that it requires restart.
Considering the configuration is set as dynamic it should take effect without a service restart.
versions
4.19.1.3
The steps to reproduce the bug
Create a truststore and set the values ldap.truststore.password and ldap.truststore
2.Add LDAPS server
Create a new truststore for different server or rename current file or create an empty one and update the configuration in the step 1.
Delete the server added in the step 2 and add it back. Or add a new LDAPS server based on the new truststore.
You will recognize that the updated values don't take effect until next service restart.
...
What to do about it?
The updated values should take effect without service restart.
The text was updated successfully, but these errors were encountered:
DaanHoogland
changed the title
Dynamic gloabl configurations for LDAPS requires restart
Dynamic global configurations for LDAPS requires restart
Feb 6, 2025
problem
The global configurations ldap.truststore.password and ldap.truststore used for enabling the SSL/TLS support for LDAP i.e LDAPS are set type dynamic and it is expected that updating them do not require cloudstack-management service restart. However this is the current behaviour.
Considering the configuration is set as dynamic it should take effect without a service restart.
versions
4.19.1.3
The steps to reproduce the bug
2.Add LDAPS server
...
What to do about it?
The updated values should take effect without service restart.
The text was updated successfully, but these errors were encountered: