Skip to content

Add LDAP upgrade instructions from users coming from 4.19.0 #408

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 21, 2024
Merged

Add LDAP upgrade instructions from users coming from 4.19.0 #408

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4efb1f3
Add LDAP upgrade instructions from users coming from 4.19.0
BryanMLima Jun 18, 2024
f65730f
Add description that the issue has been fixed and fix some typos
BryanMLima Jun 19, 2024
02fd298
Add more context
BryanMLima Jun 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions source/releasenotes/about.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,3 +118,17 @@ After identifying the snapshots with a backing store and the related templates,

.. parsed-literal::
qemu-img convert -O qcow2 -U --image-opts driver=qcow2,file.filename=<path to snapshot on secondary storage> <path to snapshot on secondary storage>-converted

Issue regarding LDAP authentication on version 4.19.0
=====================================================

In version 4.19.0, the encryption of scoped configurations of Accounts and Domains was changed to only encrypt if there were sensitive data (e.g, they belonged to the Hidden or Secure category) as all configurations for Accounts and Domains were encrypted in previous versions. However, when using the encrypted values from these scopes, ACS did not correctly decrypt these values. For this reason, a simple solution was to update these configurations to their plain values with manual DB intervention, as reported in issue `#8637`.

This issue has been fixed in Apache CloudStack 4.19.1.0. However, for users that manually set the configurations ``ldap.bind.password`` and ``ldap.truststore.password`` to a plain value in order to fix the faulty behaviour, it is required to store them encrypted after upgrading to version 4.19.1 and onwards. It will not be possible to update the configuration via UI, as an exception will be thrown when ACS tries to decrypt the plain value. To fix this, it is required to set the password again for ACS to encrypt it. There are two options:

#. Manually set the configuration via CloudMonkey, for example ``update configuration domainid=<domain-uuid> name="ldap.bind.password" value="password"``;
#. Or, removing the defined configuration through the database via the query ``DELETE from cloud.domain_details WHERE name like "%ldap%password%"``, and setting the configuration via UI for the affected domains.

After updating these configurations, LDAP authentication should be working as expected.

.. _`#8637`: https://github.com/apache/cloudstack/pull/8637