Hey, is anyone experiencing issues with the latest OpenID plugin when configured via JCasC? I followed the latest release ‘Breaking Changes’ notes and configured Jenkins with the well-known
endpoint. It works with the latest plugins on self-hosted Jenkins but doesn’t work when using Helm charts with JCasC.
The configuration below worked fine up until plugin release 4.388.v4f73328eb_d2c
securityRealm: |-
oic:
clientId: "{{ keycloak_client_id }}"
clientSecret: "{{ keycloak_client_secret }}"
automanualconfigure: "auto"
wellKnownOpenIDConfigurationUrl: "{{ keycloak_keycloak_url }}/realms/<realmName>/.well-known/openid-configuration"
userNameField: "preferred_username"
fullNameFieldName: "name"
emailFieldName: "email"
groupsFieldName: "role_list"
disableSslVerification: true
logoutFromOpenidProvider: true
overrideScopes: "openid profile email"
disableSslVerification: true
logoutFromOpenidProvider: true
postLogoutRedirectUrl: "{{ sso_keycloak_url }}/realms/<realmName>/protocol/openid-connect/logout?redirect_uri=https://www.randomweb.com"
escapeHatchEnabled: false
escapeHatchSecret: ""
tokenExpirationCheckDisabled: true
pkceEnabled: true
rootURLFromRequest: true
I also reviewed the plugin code, and it seems the wellKnownOpenIDConfigurationUrl attribute is still available.
But the logs says different things
Invalid configuration elements for type: class org.jenkinsci.plugins.oic.OicSecurityRealm : automanualconfigure,wellKnownOpenIDConfigurationUrl,overrideScopes.