> For the complete documentation index, see [llms.txt](https://docs.digitalapi.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalapi.ai/api-gateway/plugin-reference/plugins-other-protocols.md).
# Other protocols plugins
Plugins in this category handle non-HTTP protocols at the edge: gRPC transcoding, MQTT bridging, TCP-level proxying. Most gateways do not need these plugins; attach them only when you operate the underlying protocol. The catalogue ships 2 Other protocols plugins.
{% hint style="info" %}
**In this category:** [`http-dubbo`](#http-dubbo), [`kafka-proxy`](#kafka-proxy)
{% endhint %}
### `http-dubbo`
The `http-dubbo` plugin can transcode between http and Dubbo (Note: in Dubbo 2.x, the serialization type of the upstream service must be fastjson).
{% hint style="info" %}
**Priority** `504` · **Category** Other protocols · **Required** `service_name`, `method`
{% endhint %}
Configuration and details
| Name | Type | Required | Default | Valid values | Description |
| -------------------------- | ------- | -------- | ------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| service\_name | string | True | | | Dubbo service name |
| service\_version | string | False | 0.0.0 | | Dubbo service version |
| method | string | True | | | Dubbo service method name |
| params\_type\_desc | string | True | | | Description of the Dubbo service method signature |
| serialization\_header\_key | string | False | | | If `serialization_header_key` is set, the plugin will read this request header to determine if the body has already been serialized according to the Dubbo protocol. If the value of this request header is true, the plugin will not modify the body content and will directly consider it as Dubbo request parameters. If it is false, the developer is required to pass parameters in the format of Dubbo's generic invocation, and the plugin will handle serialization. Note: Due to differences in precision between Lua and Java, serialization by the plugin may lead to parameter precision discrepancies. |
| serialized | boolean | False | false | \[true, false] | Same as `serialization_header_key`. Priority is lower than `serialization_header_key`. |
| connect\_timeout | number | False | 6000 | | Upstream tcp connect timeout |
| read\_timeout | number | False | 6000 | | Upstream tcp read\_timeout |
| send\_timeout | number | False | 6000 | | Upstream tcp send\_timeout |
**Sample configuration**
Minimal transcoding to a Dubbo service method:
```json
{
"http-dubbo": {
"service_name": "org.apache.dubbo.samples.UserService",
"method": "getUser",
"params_type_desc": "java.lang.String"
}
}
```
Let each request decide whether its body is already Dubbo-serialized, read from a request header:
```json
{
"http-dubbo": {
"service_name": "org.apache.dubbo.samples.UserService",
"method": "getUser",
"params_type_desc": "java.lang.String",
"serialization_header_key": "X-Dubbo-Serialized"
}
}
```
Pinned service version, pre-serialized bodies, and tuned upstream timeouts:
```json
{
"http-dubbo": {
"service_name": "org.apache.dubbo.samples.UserService",
"service_version": "1.0.0",
"method": "getUser",
"params_type_desc": "java.lang.String",
"serialized": true,
"connect_timeout": 3000,
"read_timeout": 10000,
"send_timeout": 3000
}
}
```
### `kafka-proxy`
The `kafka-proxy` plugin can be used to configure advanced parameters for the kafka upstream of Helix, such as SASL authentication.
{% hint style="info" %}
**Priority** `508` · **Category** Other protocols
{% endhint %}
Configuration and details
| Name | Type | Required | Default | Valid values | Description |
| ------------- | ------ | -------- | ------- | --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| sasl | object | optional | | {"username": "user", "password" :"pwd"} | SASL/PLAIN authentication configuration, when this configuration exists, turn on SASL authentication; this object will contain two parameters username and password, they must be configured. |
| sasl.username | string | required | | | SASL/PLAIN authentication username |
| sasl.password | string | required | | | SASL/PLAIN authentication password |
**Sample configuration**
Attach to a Kafka upstream with no extra options:
```json
{
"kafka-proxy": {}
}
```
Enable SASL/PLAIN authentication against the Kafka upstream:
```json
{
"kafka-proxy": {
"sasl": {
"username": "kafka-user",
"password": "my-kafka-password"
}
}
}
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.digitalapi.ai/api-gateway/plugin-reference/plugins-other-protocols.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.