Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarification for CERT environment variables #395

Open
huygur opened this issue Mar 4, 2025 · 0 comments
Open

Clarification for CERT environment variables #395

huygur opened this issue Mar 4, 2025 · 0 comments

Comments

@huygur
Copy link
Contributor

huygur commented Mar 4, 2025

Camunda 8 JS SDK currently accepts following environment variables:

		/** In an environment using self-signed certificates, provide the path to the root certificate */
		CAMUNDA_CUSTOM_ROOT_CERT_PATH: {
			type: 'string',
			optional: true,
		},
		/** When using self-signed certificates, provide the root certificate as a string */
		CAMUNDA_CUSTOM_ROOT_CERT_STRING: {
			type: 'string',
			optional: true,
		},
		/** When using custom or self-signed certificates, provide the path to the certificate chain */
		CAMUNDA_CUSTOM_CERT_CHAIN_PATH: {
			type: 'string',
			optional: true,
		},
		/** When using custom or self-signed certificates, provide the path to the private key */
		CAMUNDA_CUSTOM_PRIVATE_KEY_PATH: {
			type: 'string',
			optional: true,
		},

The use case is currently not clear, and can be mistaken for the following use case:

Zeebe Gateway is encrypted using custom certification

But as discussed before, these environment variables are actually for when mTLS is used.

It will be great to clearly document this in the attached file, or in the project readme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant