Http/Https Kamelet: Expose cookieManagementDisabled parameter

[oscerd]

No description provided.

[oscerd]

This will need to create a component instance to expose the parameter. Unless there is a good reason for this, this could be parked for the moment. Creating component instances for a single parameter override, is overkilling.

[KevinMeng4662]

@oscerd

We can suspend to expose cookieManagementDisabled parameter.

I sincerely hope that can support below function.
There is actual production use case that through the CamelHttpsSinkConnector to sync the event to RemoteEndpoint.
And the RemoteEndpoint accessing must through mTLS (mutual Transport Layer Security), so need to set javax.net.ssl.keyStore, javax.net.ssl.keyStoreType, javax.net.ssl.keyStorePassword, ssl.KeyManagerFactory.algorithm parameters.

Currently if CamelHttpsSinkConnector does not expose these parameters, that we cannot support this use case.

Thanks a lot.

[oscerd]

What we could do is exposing the useSystemProperties parameters for example https://camel.apache.org/components/4.4.x/http-component.html#_using_system_properties
as first step.
Building sslContextParameters object with YAML could be a bit complex, because you need to define multiple beans to re-use in the sslContextParameters definition, so this would require a separated kamelet for the purpose.

[KevinMeng4662]

@oscerd

If adopt useSystemProperties parameters to setup CamelHttpsSinkConnector, in one JVM only can run one Connector for specific Keystore, that will waste so much resource.

Although building sslContextParameters object with YAML could be a bit complex, from the user's point of view is still very necessary.

Hope you can make plan for implementing it.

[oscerd]

It won't be in the next release 4.8.0 for sure. I'll see what is needed, you can also have a look yourself at creating a specific kamelet for this and open a PR.

[KevinMeng4662]

@oscerd I have no backgroud for creating a specific kamelet.