IMConnectionProvider.java: getAuthenticationHolder(): fix check for Bot user name… #211
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.
…to exempt empty strings (lack of specific configuration) [JENKINS-72590]
Per https://issues.jenkins.io/browse/JENKINS-72590 the check was insufficient - it only excluded
null
values, but an empty saved config conveys an empty non-null String instead.Testing done
Stumbled on this while dev-testing other PRs, and the temporary Jenkins controller had just a trivial configuration to log into IRC but only had an admin user defined locally. Replies from Jenkins for commands which required authorization, such as "help", failed with inability to "impersonate" and did not make it to IRC.
With this change, replies are present in a private chat and commands are honoured.
Submitter checklist
UPDATE: Probably this is counter-productive after all: can't assign permission constraints to a non-existing user. Would change to a more reasonable exception that helps troubleshooting instead.