This repository has been archived by the owner on Dec 13, 2022. It is now read-only.
fix(ldap): correct double slashes in the saved DN - for 19.04.x #8121
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Template
Description
The DN is escaped twice before inserting its value in the DB.
Resulting on a first successfull connection and the impossibility to connect again using the account.
As the ldapSearch method will use a DN which doesn't exist
Fixes # (none)
Type of change
Target serie
How this pull request can be tested ?
Add to your LDAP specific escaped characters (like : " , ") and manually import a contact.
The contact will be displayed in the list, but in the DB, the contact_ldap_dn will have two slashes.
Checklist
Community contributors & Centreon team
Centreon team only