Andrea Cosentino created CAMEL-27096:
----------------------------------------

             Summary: camel-main - camel.vault.cyberark.verifySsl is documented 
with the default false, and has no insecure:ssl marker
                 Key: CAMEL-27096
                 URL: https://issues.apache.org/jira/browse/CAMEL-27096
             Project: Camel
          Issue Type: Bug
          Components: camel-main
            Reporter: Andrea Cosentino


Follow-up of CAMEL-26279 ([PR 
#29210|https://github.com/apache/camel/pull/29210]), found while fixing it.

{{CyberArkVaultConfiguration.verifySsl}} in camel-api (main 73fe55b4f931, lines 
41-42) is {{true}} by default, but the camel-main metadata documents 
{{camel.vault.cyberark.verifySsl}} with {{"defaultValue": false}} 
(camel-main-configuration-metadata.json, line 587), and so do the pages and 
tools built from it. The field has a bare {{@Metadata}}: 
{{PrepareCamelMainMojo}} then takes the default from the annotation instead of 
the field initializer (lines 93-98), and documents a boolean without one as 
{{false}} (lines 246-247). It looks like the only such option in camel-main and 
the vault configurations.

The field has no {{security}} marker either, unlike 
{{camel.ssl.trustAllCertificates}} ({{@Metadata(security = "insecure:ssl")}}). 
So the camel-main metadata does not show the option as {{insecure:ssl}}, and 
{{SecurityUtils}} has no key for it: a match relies on {{verifySsl}} being an 
{{insecure:ssl}} option name of the cyberark-vault and ibm-watsonx-ai 
components.

Proposed: {{@Metadata(defaultValue = "true", security = "insecure:ssl", 
insecureValue = "false")}} on the field, then regenerate the camel-main 
metadata, its catalog copy and {{SecurityUtils}} (the last one needs the full 
reactor).

_Claude Code on behalf of Andrea Cosentino (oscerd)_



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to