Jenkins controller breaks with the new version of the plugin 4.355.v3a_fb_fca_b_96d4

[kashyap92]

Jenkins and plugins versions report

Jenkins controller version: 2.462.3
OS: Amazon Linux 2023.5.20240916
oic-auth plugin version: 4.355.v3a_fb_fca_b_96d4

After updating the plugin, Jenkins controller fails with

HTTP ERROR 503 java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong.
URI:/STATUS:503MESSAGE:java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong.SERVLET:StaplerCAUSED BY:java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong.

What Operating System are you using (both controller, and any agents involved in the problem)?

Jenkins controller version: 2.462.3
OS: Amazon Linux 2023.5.20240916
oic-auth plugin version: 4.355.v3a_fb_fca_b_96d4

Reproduction steps

Step 1. Update oic-auth plugin to v4.355.v3a_fb_fca_b_96d4
Step 2. Access Jenkins from UI

Expected Results

Jenkins controller should be accessible.

Actual Results

HTTP ERROR 503 java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong.
URI:/STATUS:503MESSAGE:java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong.SERVLET:StaplerCAUSED BY:java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong.

Anything else?

No response

Are you interested in contributing a fix?

No response

[eva-mueller-coremedia]

I updated to the latest plugin (4.371.vc7c0c06e8a_f5) yesterday (Jenkins: 2.462.3) and had no issues.

• Could you post the complete stacktrace? That would be great.
• Which was the last working version you had installed? I am asking this due to breaking changes (see https://github.com/jenkinsci/oic-auth-plugin/releases/tag/4.355.v3a_fb_fca_b_96d4 and here https://github.com/jenkinsci/oic-auth-plugin/releases/tag/4.350.v347c3b_8b_9d95)

[TomHellier]

I'm seeing similar, I will attempt to change my configurationas my jcasc configuration is no longer valid based on this PR.

#399

Yes - updating my JCasC configuration based on the changes in the linked PR has resolved the issue.

Thanks @eva-mueller-coremedia

To help future viewers, this was the error so search engines can scrape it.

io.jenkins.plugins.casc.UnknownAttributesException: oic: Invalid configuration elements for type: class org.jenkinsci.plugins.oic.OicSecurityRealm : authorizationServerUrl,tokenServerUrl,scopes.
Available attributes : allowTokenAccessWithoutOicSession, allowedTokenExpirationClockSkewSeconds, captchaSupport, clientId, clientSecret, disableSslVerification, disableTokenVerification, emailFieldName, escapeHatchEnabled, escapeHatchGroup, escapeHatchSecret, escapeHatchUsername, fullNameFieldName, groupsFieldName, logoutFromOpenidProvider, nonceDisabled, pkceEnabled, postLogoutRedirectUrl, rootURLFromRequest, sendScopesInTokenRequest, serverConfiguration, tokenExpirationCheckDisabled, tokenFieldToCheckKey, tokenFieldToCheckValue, userNameField

[jtnord]

release notes have been updated to copy the details that where previously available if following the links into the actual release note