oscerd opened a new pull request, #29137: URL: https://github.com/apache/camel/pull/29137
Fixes [CAMEL-26561](https://issues.apache.org/jira/browse/CAMEL-26561). Documentation only. **camel-opa, "Connecting to the server".** The example that presents a SPIFFE X.509-SVID to an OPA server built a `SpiffeSSLContextParameters` with neither `acceptedSpiffeIds` nor `acceptAnySpiffeId`. `createSSLContext` fails closed in that case, so a route using it did not start. The example now pins the OPA server's SPIFFE ID, drops the `setCamelContext` call it does not need (`createSSLContext` sets the context), gets a YAML tab, and a short paragraph says why the peer constraint is required and where the Workload API address comes from. **camel-spiffe.** The `SpiffeSSLContextParameters` and `SpiffeSecurityPolicy` examples were Java only, while the opa and openfga pages give every example in Java and YAML. They now have YAML tabs, including the `serverParameters.clientAuthentication: REQUIRE` the server side needs and the `opaPolicy` bean the SPIFFE-then-OPA example uses. The catalog copies of both pages are updated to match (byte-identical). ### Verification - Every new YAML block passes the YAML DSL schema validation. - With `camel run --camel-version=4.23.0 --dep=camel:opa,camel:spiffe` and an `opa:` endpoint using `sslContextParameters=#opaTls`: - the old example fails at startup with `A SPIFFE-backed SSLContext requires either acceptAnySpiffeId=true or a non-empty acceptedSpiffeIds allow-list`; - the new one passes that check and stops only at the Workload API (`Endpoint Socket Address Environment Variable is not set: SPIFFE_ENDPOINT_SOCKET`), as expected without a SPIRE agent. No code change. Related YAML work on these components: CAMEL-26559, CAMEL-26560, CAMEL-26562. _Claude Code on behalf of oscerd_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
