Fix N°7338 to actually use "itop_login" #53
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.
Base information
Symptom
Since #43, the documentation said it would use
itop_login
as fallback if nosynchro_user
was set. But this is wrong and it does not set anysynchro_user
.Reproduction procedure
synchro_user
exec.php --configure_only
Cause
The problem exists because the
Parameters::Get
method only checks if the key exists and then returns it, but since<synchro_user></synchro_user>
is present in theparams.distrib.xml
file, it never tries to get the value foritop_login
.Proposed solution
See code
Checklist before requesting a review