-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Not A Defect
-
Component/s: active-directory-plugin, configuration-as-code-plugin
-
Labels:None
-
Environment:jenkins:2.150.2
configuration-as-code-support:1.5
configuration-as-code:1.5
active-directory:2.11
-
Similar Issues:
The issue appeared after updating active-directory plugin to 2.11 which is a security update. Downgrade to active-directory:2.10 resolves the issue.
Jenkins startup fails due to JCasC complaining about invalid configuration element: tlsConfiguration
Caused by: io.jenkins.plugins.casc.ConfiguratorException: Invalid configuration elements for type class hudson.plugins.active_directory.ActiveDirectorySecurityRealm : tlsConfiguration. Available attributes : bindName, bindPassword, cache, captchaSupport, customDomain, domain, domains, environmentProperties, groupLookupStrategy, internalUsersDatabase, removeIrrelevantGroups, server, site, startTls
If TLS is not configured it defaults to (Unsecure) Trust all Certificates option.
I tried and it does work, thanks Gordon Franke!
I did not notice the tlsConfiguration moved from activeDirectory level to domain level. I suppose this can be closed then.
try this it works for me
securityRealm:
activeDirectory:
domains:
- bindName: "CN=..."
bindPassword: "{...}"
name: "your.domain"
tlsConfiguration: TRUST_ALL_CERTIFICATES
cache:
size: 256
ttl: 3600
groupLookupStrategy: RECURSIVE
startTls: true
Edgars Didrihsons thank you for the feedback. Yes we moved it to have a more secure approach.
Gordon Franke thank you for the help there!