DevOps Service Hook breaks after upgrading plugins and Jenkins

Jenkins setup:
Jenkins 2.426.3
Tomcat on Windows running as a service (war)

We are upgrading Jenkins to v2.462.2 and have several plugins that need to be upgraded as well. When we made a first attempt the service hooks in DevOps server that had worked before the upgrade now can’t authenticate. I traced this to the git plugin. We have been running version 4.11.3 and if I simply upgrade that plugin alone, leaving everything else the same, I reproduce the problem.

There are two articles already referencing this issue:

Good information, but it doesn’t get me to exactly what I need to do. Is the recommendation to make a change in DevOps server? Is there something I need to configure on Jenkins server or both. I understand passing the token but need just a little more help to move forward.

The second item you referenced seems like the most likely for your case. See my answer there.

We also had a same issue when we upgraded our Jenkins to 2.462.1 LTS. Please run below groovy script in script console of Jenkins for temporary fix:
hudson.plugins.git.GitStatus.NOTIFY_COMMIT_ACCESS_CONTROL=‘disabled-for-polling’

Permanent fix:
add below system property in catalina.sh (in your case it should be catalina.bat)
JAVA_OPTS=“$JAVA_OPTS -Dhudson.plugins.git.GitStatus.NOTIFY_COMMIT_ACCESS_CONTROL=disabled-for-polling”

Note: Make sure to restart Jenkins for permanent fix to apply.

Thanks Pradip and Mark. I have a separate post on this under a different topic, but noting that I did try the “permanent fix” offered as a test and that didn’t seem to help me. Regardless, we need the most secure potion, which means we need to figure out how to modify our service hooks in DevOps Server to properly pass the required information. I’d also prefer not relying on an admin account/token, but just the token in the Global Security. I’m close, but not quite close enough. Much appreciated.