Integrations
Set up Schema Registry credentials in Duaer
Store Schema Registry 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 a Schema Registry
The Duaer Schema Registry credential lets the Kafka and Kafka Trigger nodes encode and decode Avro messages:
- URL is the Schema Registry address, such as https://schema-registry-domain:8081.
- Self-hosted, Username and Password are the registry account. On Confluent Cloud, use the API key and secret created for Schema Registry, which differ from the Kafka cluster keys.
Schema Registry fields in Duaer
In Duaer, choose Schema Registry when you create a credential, then fill in these fields:
- URL (required): URL of the schema registry.
- Authentication: Default: Basic Auth. Options: Basic Auth, None.
- Username (required): Username or Confluent Cloud API key. Shown when Authentication is Basic Auth.
- Password (required, secret): Password or Confluent Cloud API secret. Shown when Authentication is Basic Auth.
When you save, Duaer tests the connection with these values.
Duaer nodes that use it: Kafka, Kafka Trigger.
Save the connection in Duaer
Open Credentials and create Schema Registry. 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.
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 Schema Registry secret values appear in Duaer node parameters?
No. In Duaer, Schema Registry secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Schema Registry 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 Schema Registry expects, then confirm you can create credentials in that project.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a digital organization. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.