Duaer

Integrations

Set up Kafka credentials in Duaer

Store Kafka connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.

Connect to Kafka

The Duaer Kafka credential:

  • Brokers takes one or more host:port entries, comma-separated, such as kafka1:9092,kafka2:9092.
  • Client ID only labels this client in Kafka logs; it does not affect the connection.
  • SSL is on by default. Turn it off for a local or private Kafka without encryption, or the connection fails.
  • For authentication, turn on Authentication, fill in Username and Password, and pick the SASL Mechanism the brokers use: Plain, scram-sha-256, or scram-sha-512.

For Confluent Cloud: put the cluster’s bootstrap server in Brokers, turn on SSL and Authentication, use the API key as Username and the API secret as Password, and pick Plain.

Kafka fields in Duaer

In Duaer, choose Kafka when you create a credential, then fill in these fields:

  • Client ID: Will not affect the connection, but will be used to identify the client in the Kafka server logs. Read more here (https://kafka.apache.org/documentation/#design_quotasgroups)
  • Brokers
  • SSL: Default: on.
  • CA Certificate (secret): PEM-encoded CA certificate(s) used to verify the broker. Leave empty to use the system CAs. Shown when SSL is on.
  • Client Certificate (secret): PEM-encoded client certificate for mutual TLS (mTLS). Provide together with the client private key. Shown when SSL is on.
  • Client Private Key (secret): PEM-encoded client private key for mutual TLS (mTLS). Provide together with the client certificate. Shown when SSL is on.
  • Ignore SSL Issues (Insecure): Whether to connect even when SSL certificate validation fails (e.g. a self-signed or hostname-mismatched broker certificate) Default: off. Shown when SSL is on.
  • Authentication: Default: off.
  • Username: Optional username if authenticated is required. Shown when Authentication is on.
  • Password (secret): Optional password if authenticated is required. Shown when Authentication is on.
  • SASL Mechanism: Default: Plain. Options: Plain, scram-sha-256, scram-sha-512. Shown when Authentication is on.

Duaer nodes that use it: Kafka, Kafka Trigger.

Save the connection in Duaer

Open Credentials and create Kafka. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. The matching node is under the related node.

Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.

Questions

Do Kafka secret values appear in Duaer node parameters?

No. In Duaer, Kafka secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

What usually stops a Kafka credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Kafka expects, then confirm you can create credentials in that project.

In this section