-
New Feature
-
Resolution: Unresolved
-
Minor
-
Jenkins 2.462.3 (from docker image lts-jdk21)
Active Directory plugin Version2.37
Note: Whereas this was mentioned in JENKINS-71170, that issue did not request a change.
The log messages introduced for the resolution of JENKINS-42687 are very noisy. The comments above the logging calls suggest that these are not failures but they are sent at Level.WARNING and cannot be disabled via a Java option like is done with `-Dorg.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.ADMIN_AUTO_APPROVAL_ENABLED=true`.
I can see two options off the top of my head that would help:
- downgrade to `LogLevel.FINE` (or lower)
- enable the logging to be disabled via a Java property (a la `ADMIN_AUTO_APPROVAL_ENABLED`)? (this might be more useful, if the default behavior is to log these messages - some people might find it useful).
the two log messages are here:
https://github.com/search?q=repo%3Ajenkinsci%2Factive-directory-plugin%20JENKINS-42687&type=code
The noisiness is an issue for us, too. It's filling up the logs for no good reason.
In addition to the proposed options above, I could see a configurtion setting, e.g. "Warn on partial result exceptions (see
JENKINS-42687)" as a boolean flag.By the way, we are seeing this with Windows Server 2019. Thus, the comment in
JENKINS-42687about a potential fix through a Windows Server update seems irrelevant:I had difficulties on understanding why this is happening, but according to Spring LDAP it seems that it might be a common situation on some Windows Server. Folks also said that applying a Windows Update might fix the problem.
Even more so I see no point in logging this exception as-is.
https://github.com/jenkinsci/active-directory-plugin/blob/5598d1621518b1d761e3824dc3844a4201289cca/src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java#L802-L806