Skip to main content

Hello,

In a Cribl Distributed Deployment, with one Worker Group, and 2 Worker Nodes in this Worker Group, with a Source Splunk TCP enabled, and TLS enabled from Leader Node, It is not possible to use a unique certificate and passphrase for each Worker Node.
It is possible, to have each Worker Node in a different Worker Group. But that means all the settings must be the same (Sources, Destination, Routes, Pipelines). That means in the end that the use of Leader Node is useless.
Is that correct?
Can we improve that? Or make an enhancement?

Thank you!
Best regards,
Vali

You can specify the location of the keypair on the filesystem. Then you only need to make sure every worker has their unique key in the right location. It just means youre not using the Leader to manage this part. The pic below is from a source config TLS screen:

217_07b2c92e6e6c459aa85914541dd9ce7a.png

Hello John,

Is this topic on the roadmap so far?

Thanks!

Does anyone know if the implementation of using different passphrases for each certificate is on the roadmap?

Hi @Jon Rust
Is the implementation of using different passphrases for each certificate on the roadmap?

Hi @Jon Rust any news here?

There isn't a current plan to add support for unique certs per worker in a worker group.

Reply


Terms & ConditionsCookie settings