You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User reports that when Redis requires authentication, the getRedisUri() method in org/apache/rocketmq/connect/redis/common/Config.java does not include the password in the URI, causing authentication failures.
Analysis
This is a valid bug. The Redis URI construction is missing the password component, which is required for authenticated Redis connections. The suggested fix is to add password authentication to the URI format: redis://:password@host:port.
Additionally, the user notes that the redis.replicator.version may be outdated and only supports Redis 6.
Suggestions
Update getRedisUri() to include password authentication in the URI format
Consider upgrading the Redis replicator version for better Redis version compatibility
Add unit tests for authenticated Redis connections
Verdict
Valid bug — Redis connector fails to handle authenticated connections. Requires code fix to include password in URI construction.
Root Cause:Config.getRedisUri() does not include the password in the URI format when Redis authentication is enabled. The URI should be redis://:password@host:port for authenticated connections. Impact: Functional — Redis connector fails with authentication error when password is configured Severity: Medium
Valid issue. The fix should update getRedisUri() to append :${redisPassword}@ before the host when password is configured. The replicator version compatibility with Redis 6+ is a separate concern.
An automated fix proposal will be generated. Reply /approve to proceed with PR generation.
This issue evaluation has timed out — no community feedback was received within the 72-hour window.
The analysis and proposed fix remain available in the earlier comment for anyone who would like to pick it up. If a maintainer or contributor wants to proceed, feel free to open a PR referencing this issue.
Closing the automated workflow. Thank you for your understanding!
Feedback Timeout\n\nNo feedback was received within 72 hours. The automated fix proposal has been closed.\n\nIf you'd like to proceed with a fix, please reply to this issue and a maintainer will review it.\n\n---\nAutomated timeout by RockteMQ-AI
The Redis connector's getRedisUri() method does not include the password in the URI when Redis requires authentication. The fix is straightforward — append :password@ to the URI before the host.
Root Cause: Missing password segment in the Redis URI construction in Config.java.
Suggested Fix:
sb.append(":").append(redisPassword).append("@");
Additionally, the redis.replicator.version may need updating for broader Redis compatibility.
The Redis connector not handling password authentication is a real issue that prevents connecting to password-protected Redis instances.
Root Cause: Missing password field handling in the Redis connector configuration. Impact: Functionality — cannot connect to secured Redis instances. Severity: medium
Activity
oss-sentinel-ai commentedon Jun 8, 2026
Assessment by github-manager-bot
Type: Bug
Priority: Medium
Summary
User reports that when Redis requires authentication, the
getRedisUri()method inorg/apache/rocketmq/connect/redis/common/Config.javadoes not include the password in the URI, causing authentication failures.Analysis
This is a valid bug. The Redis URI construction is missing the password component, which is required for authenticated Redis connections. The suggested fix is to add password authentication to the URI format:
redis://:password@host:port.Additionally, the user notes that the
redis.replicator.versionmay be outdated and only supports Redis 6.Suggestions
getRedisUri()to include password authentication in the URI formatVerdict
Valid bug — Redis connector fails to handle authenticated connections. Requires code fix to include password in URI construction.
Automated assessment by github-manager-bot
RockteMQ-AI commentedon Aug 5, 2026
Issue Evaluation
Category:
bug| Status: ConfirmedRoot Cause:
Config.getRedisUri()does not include the password in the URI format when Redis authentication is enabled. The URI should beredis://:password@host:portfor authenticated connections.Impact: Functional — Redis connector fails with authentication error when password is configured
Severity: Medium
Valid issue. The fix should update
getRedisUri()to append:${redisPassword}@before the host when password is configured. The replicator version compatibility with Redis 6+ is a separate concern.An automated fix proposal will be generated. Reply
/approveto proceed with PR generation.Automated evaluation by @RockteMQ-AI
RockteMQ-AI commentedon Aug 10, 2026
This issue evaluation has timed out — no community feedback was received within the 72-hour window.
The analysis and proposed fix remain available in the earlier comment for anyone who would like to pick it up. If a maintainer or contributor wants to proceed, feel free to open a PR referencing this issue.
Closing the automated workflow. Thank you for your understanding!
RockteMQ-AI commentedon Aug 10, 2026
Feedback Timeout\n\nNo feedback was received within 72 hours. The automated fix proposal has been closed.\n\nIf you'd like to proceed with a fix, please reply to this issue and a maintainer will review it.\n\n---\nAutomated timeout by RockteMQ-AI
RockteMQ-AI commentedon Aug 18, 2026
Issue Evaluation
Category:
bug| Status: ConfirmedThe Redis connector's
getRedisUri()method does not include the password in the URI when Redis requires authentication. The fix is straightforward — append:password@to the URI before the host.Root Cause: Missing password segment in the Redis URI construction in
Config.java.Suggested Fix:
Additionally, the
redis.replicator.versionmay need updating for broader Redis compatibility.Automated evaluation by RockteMQ-AI
RockteMQ-AI commentedon Sep 4, 2026
Issue Evaluation
Category:
bug| Status: ConfirmedThe Redis connector not handling password authentication is a real issue that prevents connecting to password-protected Redis instances.
Root Cause: Missing password field handling in the Redis connector configuration.
Impact: Functionality — cannot connect to secured Redis instances.
Severity: medium
Automated evaluation by github-manager-bot