apache / apache/iotdb

[Feature request] Make MQTT Service's Anonymous Access Configurable

Open
#14,785 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
6.4k
Forks
1.2k
Avg merge
1d 23h
Merged PRs (30d)
115

Description

### Search before asking

- [x] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar.

### Motivation

I noticed in this PR: https://github.com/apache/iotdb/pull/1447 that anonymous access (`ALLOW_ANONYMOUS_PROPERTY_NAME`) to the MQTT service was added. Is there any plan to make it configurable?

My use case is that I have an MQTT client to which I do not have access to its source code, and it sends data to the MQTT broker using a specific username. I would like to make the MQTT service anonymously accessible.

---

我注意到在这个 PR:https://github.com/apache/iotdb/pull/1447 中,已添加了对 MQTT 服务的匿名访问(`ALLOW_ANONYMOUS_PROPERTY_NAME`)。是否有计划使其可配置?

我的使用场景是,我有一个 MQTT 客户端,但无法访问其源代码,该客户端使用特定的用户名将数据发送到 MQTT 经纪服务器。我希望使 MQTT 服务可以匿名访问。

### Solution

_No response_

### Alternatives

_No response_

### Are you willing to submit a PR?

- [x] I'm willing to submit a PR!

Contributor guide

Open the contributing guide

Research direction

Start by tracing ALLOW_ANONYMOUS_PROPERTY_NAME through the MQTT service configuration and compare the behavior introduced in PR 1447. The change is done when anonymous access can be controlled through configuration while existing MQTT authentication behavior remains correct; the payload names no specific test or file to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
databases
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.